Home
last modified time | relevance | path

Searched refs:tracing (Results 1 – 7 of 7) sorted by relevance

/system/extras/tests/mmc_tracepoints/
DREADME2 in the kernel. To turn on mmc tracing, do this:
4 adb shell echo 1 >/d/tracing/events/mmc/enable
5 adb shell echo 1 >/d/tracing/tracing_on
9 adb pull /d/tracing/trace
13 adb shell echo 0 >/d/tracing/tracing_enabled
/system/extras/ANRdaemon/
DREADME3 logging. Trace are configured ahead by setting different modules in /d/tracing.
6 /d/tracing/trace.
11 This means tracing will be enabled above 99.90% CPU utilization and will trace
20 not running. This is because the daemon process turns off tracing when CPU usage
23 when the CPU usage becomes high and the daemon process turn on tracing again,
24 the first entry in /d/tracing/trace logged by sched is switching away from the
DANRdaemon.cpp87 static bool tracing = false; variable
162 int threshold = idle_threshold + (tracing?100:0); in is_heavy_load()
257 tracing = true; in start_tracing()
269 tracing = false; in start_tracing()
329 while (tracing) { in dump_trace()
/system/sepolicy/
Datrace.te13 # atrace reads the files in /sys/kernel/debug/tracing/
Dinit.te116 # Disable tracing by writing to /sys/kernel/debug/tracing/tracing_on
Dfile_contexts383 /sys/kernel/debug/tracing(/.*)? u:object_r:debugfs_tracing:s0
384 /sys/kernel/debug/tracing/trace_marker u:object_r:debugfs_trace_marker:s0
Ddomain.te135 # Almost all processes log tracing information to
136 # /sys/kernel/debug/tracing/trace_marker