Menu
▾
▴
Tree [eb790e] marshmallow-x86 android-x86-6.0-r1 android-x86-6.0-r2 android-x86-6.0-r3 / tests / mmc_tracepoints / History
| File | Date | Author | Commit |
|---|---|---|---|
| README | 2013-05-17 |
Ken Sumrall
|
[6fa80f] Tools to analyze mmc tracepoint data from the k... |
| mmc_trace_reduce | 2013-05-17 |
Ken Sumrall
|
[6fa80f] Tools to analyze mmc tracepoint data from the k... |
| mmc_trace_sample_data | 2013-05-17 |
Ken Sumrall
|
[6fa80f] Tools to analyze mmc tracepoint data from the k... |
Read Me
The code in this directory is used to process data from the mmc tracepoints in the kernel. To turn on mmc tracing, do this: adb shell echo 1 >/d/tracing/events/mmc/enable adb shell echo 1 >/d/tracing/tracing_on To get the trace: adb pull /d/tracing/trace To turn it back off, do: adb shell echo 0 >/d/tracing/tracing_enabled The output is in a form of start/stop pairs. The ops with rw in the name are read or write ops, and the ones with erase in the name are the various erase opts. The mmc_trace_reduce script will take the output from the kernel, and convert it to a single line per event, which includes the duration of the event. This can then be fed into other tools for further analysis. The file mmc_trace_sample_data contains sample mmc trace data from a Nexus 10. It includes read, write and discard entries. The discard entries came from invoking fstrim in vold with "vdc fstrim dotrim".
