summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTreehugger Robot <treehugger-gerrit@google.com>2021-09-20 18:32:55 +0000
committerGerrit Code Review <noreply-gerritcodereview@google.com>2021-09-20 18:32:55 +0000
commitfd8d5fdeb83e9d1d7d2f7d9ce31fb524c7572552 (patch)
tree471780e379c5ef654e8b00ee23f6358c8dfdc329
parentbe271379f695c222db3aaab76ea280d92819bc8c (diff)
parent1c7d0bee99a06453fd553e675a1e6403fb414663 (diff)
downloadextras-fd8d5fdeb83e9d1d7d2f7d9ce31fb524c7572552.tar.gz
Merge "Remove code block for bullet points that aren't code."
-rw-r--r--simpleperf/doc/README.md11
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