diff options
author | Mark Hansen <markhansen@google.com> | 2021-09-20 00:33:51 +0000 |
---|---|---|
committer | Mark Hansen <markhansen@google.com> | 2021-09-20 00:33:59 +0000 |
commit | 1c7d0bee99a06453fd553e675a1e6403fb414663 (patch) | |
tree | 2bf0bc7d3e59f277bb269e604832fd7fde0cb71b | |
parent | c57a063a79ee6279bccbf6889f2d85caa6309cd9 (diff) | |
download | extras-1c7d0bee99a06453fd553e675a1e6403fb414663.tar.gz |
Remove code block for bullet points that aren't code.
It looked a bit funny when rendered to markdown before.
Change-Id: Iacbc310812c0304c6355c0fe751a56049593cf25
-rw-r--r-- | simpleperf/doc/README.md | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/simpleperf/doc/README.md b/simpleperf/doc/README.md index 39207c67..853a2852 100644 --- a/simpleperf/doc/README.md +++ b/simpleperf/doc/README.md @@ -115,16 +115,15 @@ See [scripts_reference.md](./scripts_reference.md). ## Answers to common issues ### Why we suggest profiling on Android >= N devices? -``` + 1. Running on a device reflects a real running situation, so we suggest -profiling on real devices instead of emulators. + profiling on real devices instead of emulators. 2. To profile Java code, we need ART running in oat mode, which is only -available >= L for rooted devices, and >= N for non-rooted devices. + available >= L for rooted devices, and >= N for non-rooted devices. 3. Old Android versions are likely to be shipped with old kernels (< 3.18), -which may not support profiling features like recording dwarf based call graphs. + which may not support profiling features like recording dwarf based call graphs. 4. Old Android versions are likely to be shipped with Arm32 chips. In Arm32 -mode, recording stack frame based call graphs doesn't work well. -``` + mode, recording stack frame based call graphs doesn't work well. ### Suggestions about recording call graphs |