Lines Matching refs:trace

4 Depending on the CPU usage level, the trace is turn on/off by writting to the
5 global control /d/trace/trace_on. The raw trace file is stored at
6 /d/tracing/trace.
11 This means tracing will be enabled above 99.90% CPU utilization and will trace
14 Use ANRdaemon_get_trace.sh [device serial] to dump and fetch the compressed trace file.
16 The compressed trace file can be parsed using systrace:
17 $ systrace.py --from-file=<path to compressed trace file>
19 Known issue: in the systrace output, anrdaemon will show up when the trace is
21 drops, the last entry it leaves in the raw trace file is the scheduler switched
24 the first entry in /d/tracing/trace logged by sched is switching away from the
25 daemon process to some other process. Due to this artifact, when the raw trace
27 whole 20secs (because from systrace's view, the two 20 sec apart sched trace
29 for all 20sec). However, this will not affect the actual captured trace during