Lines Matching +refs:is +refs:pre +refs:merge
49 This tool suite is designed to assist kernel and OS developers in optimizing
52 and will capture dmesg and ftrace data. This data is transformed into a set of
61 - runs with python2 or python3, choice is made by /usr/bin/python link
97 (kernel/pre-3.15/enable_trace_events_suspend_resume.patch)
98 (kernel/pre-3.15/enable_trace_events_device_pm_callback.patch)
112 There is a patch which does this for kernel v3.8.0:
113 (kernel/pre-3.11-rc2/enable_ftrace_in_suspendresume.patch)
160 timeline. This is useful in discovering dependent threads to get a better
161 idea of what each device is waiting for. For instance, the scsi_eh thread,
162 a.k.a. scsi resume error handler, is what each SATA disk device waits for
179 Proc mode adds user process info to the timeline. This is done in a manner
203 The best way to gauge the health of a system is to run a series of
215 file is a tabular list of the tests with relevant info and links. The
245 run is done, the -summary command is called automatically to create summary
257 These are the relevant commands to use after testing is complete:
262 current folder. summary.html is a table of tests with relevant info sorted
264 is a list of kernel issues found in dmesg from all the tests.
265 summary-devices.html is a list of devices and times from all the tests.
275 A multitest is initiated like this:
288 The summary for an existing multitest is generated like this:
394 # Expand Callgraph: pre-expand the callgraph treeviews in html (def: false)
417 # merge loops of the same call if each is less than maxgap apart (def: 100us)
421 # merge loops of the same call if each is less than maxlen in length (def: 5ms)
434 in the timeline to show you where the time is going. These calls should fill
435 the timeline with contiguous data so that most kernel execution is covered.
437 It is possible to add new function calls to the timeline by adding them to
450 an argument list, and a color. But only a function name is required.
462 function: The symbol name for the function you want probed, this is the
475 color: The color of the entry block in the timeline. The default color is
476 transparent, so the entry shares the phase color. The color is an
486 Here is a full example entry. It displays cpu resume calls in the timeline
500 timeline. However, if a function call is not within a main timeline event,
511 It is possible to add new function calls to the dev timeline by adding them
520 The format is the same as the timeline_functions_x86_64 section. It's a
525 and a color. But only the function name is required.
531 Here is a full example entry. It displays the ATA port reset calls as
532 ataN_port_reset in the timeline. This is where most of the SATA disk resume
557 is sysfs mounted: YES
558 is "mem" a valid power mode: YES
559 is ftrace supported: YES
562 is rtcwake supported: YES
593 The easiest way to execute on an android device is to run the android.sh
622 # the above is what you see on a system that's properly patched
649 # (required) get the ftrace data, this is the most important piece
651 # (optional) get the dmesg data, this is for debugging