Lines Matching full:timeline

38 	- Custom Timeline Entries
39 		- Adding/Editing Timeline Functions
40 		- Adding/Editing Dev Timeline Source Functions
142  be used to regenerate the html timeline with different options
154  Developer mode adds information on low level source calls to the timeline.
157  subsystem dependent calls to better fill out the timeline.
160  timeline. This is useful in discovering dependent threads to get a better
165  The timeline will be much larger if run with dev mode, so it can be useful
179  Proc mode adds user process info to the timeline. This is done in a manner
240 	Add kernel source calls and threads to the timeline (default: disabled).
252 	Run the test and capture the trace logs, but skip the timeline and summary
279 	or you can skip timeline generation in order to speed things up
284  Each test subfolder contains the dmesg/ftrace logs and/or the html timeline
306 	Simple suspend/resume with basic timeline (mem/freeze/standby)
311 	Dev mode suspend/resume with dev timeline (mem/freeze/standby)
316 	Simple suspend/resume with timeline and callgraph (mem/freeze/standby)
324 	Sample for editing timeline funcs (moves internal functions into config)
325 		config/custom-timeline-functions.cfg
364  # Sus/Res Gap: insert a gap between sus & res in the timeline (def: false)
370  # Proc mode: graph user processes and cpu usage in the timeline (def: false)
373  # Dev mode: graph source functions in the timeline (def: false)
391  # Callgraph: gather ftrace callgraph data on all timeline events (def: false)
406  # Override default timeline entries:
407  # Do not use the internal default functions for timeline entries (def: false)
409  override-timeline-functions: true
411  # Override default dev timeline entries:
412  # Do not use the internal default functions for dev timeline entries (def: false)
414  override-dev-timeline-functions: true
425 |                   CUSTOM TIMELINE ENTRIES                      |
428 Adding or Editing Timeline Functions
432  timeline where device callbacks don't appear. For instance, in suspend_prepare
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
438  the config. It's also possible to copy the internal timeline functions into
443  Use the override-timeline-functions option if you only want to use your
452  For a full example config, see config/custom-timeline-functions.cfg. It pulls
453  all the internal timeline functions into the config and allows you to edit
470     format: The format to display the data on the timeline in. Use braces to
475     color: The color of the entry block in the timeline. The default color is
486  Here is a full example entry. It displays cpu resume calls in the timeline
493 Adding or Editing Dev Mode Timeline Source Functions
497  execution within the timeline entries.
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
512  to the config. It's also possible to copy the internal dev timeline
517  Use the override-dev-timeline-functions option if you only want to use your
527  For a full example config, see config/custom-timeline-functions.cfg. It pulls
528  all the internal dev timeline functions into the config and allows you to edit
532  ataN_port_reset in the timeline. This is where most of the SATA disk resume
554  sudo ./sleepgraph.py -config config/custom-timeline-functions.cfg -status
561     timeline data source: FTRACE (all trace events found)
563     verifying timeline kprobes work: