diff options
| author | Yasuhiro Matsuda <mazda@google.com> | 2015-06-15 18:49:35 +0900 |
|---|---|---|
| committer | Yasuhiro Matsuda <mazda@google.com> | 2015-07-29 12:53:05 +0900 |
| commit | f93db4b827818806ca4cee80e6ec954d7aa40632 (patch) | |
| tree | d85c17262e66da10f1000b54513d6d6ee31ebce9 /libcutils | |
| parent | c0e8d0fc50dc635c6723497900cf3b0d2eb572dc (diff) | |
| download | core-f93db4b827818806ca4cee80e6ec954d7aa40632.tar.gz core-f93db4b827818806ca4cee80e6ec954d7aa40632.tar.bz2 core-f93db4b827818806ca4cee80e6ec954d7aa40632.zip | |
Introduce a mechanism to trace boot sequence.
This CL adds a trigger and a service so that Systrace can be used
for tracing events during boot.
persist.debug.atrace.boottrace property is used for switching on
and off tracing during boot. /data/misc/boottrace/categories
file is used for specifying the categories to be traced.
These property and file are rewritten by Systrace when the newly
added option --boot is specified.
Here is an example of tracing events of am and wm catetories
during boot.
$ external/chromium-trace/systrace am wm --boot
This command will cause the device to reboot. Once the device has
booted up, the trace report is created by hitting Ctrl+C.
As written in readme.txt, this mechanism relies on persistent
property, so tracing events that are emitted before that are not
recorded. This is enough for tracing events after zygote is
launched though.
This only works on userdebug or eng build for security reason.
BUG: 21739901
Change-Id: I03f2963d77a678f47eab5e3e29fc7e91bc9ca3a4
Diffstat (limited to 'libcutils')
0 files changed, 0 insertions, 0 deletions