Lines Matching refs:timeline

136  be used to regenerate the html timeline with different options
148  Developer mode adds information on low level source calls to the timeline.
151  subsystem dependent calls to better fill out the timeline.
154  timeline. This is useful in discovering dependent threads to get a better
159  The timeline will be much larger if run with dev mode, so it can be useful
173  Proc mode adds user process info to the timeline. This is done in a manner
202 	Simple suspend/resume with basic timeline (mem/freeze/standby)
207 	Dev mode suspend/resume with dev timeline (mem/freeze/standby)
212 	Simple suspend/resume with timeline and callgraph (mem/freeze/standby)
220 	Sample for editing timeline funcs (moves internal functions into config)
221 		config/custom-timeline-functions.cfg
260  # Sus/Res Gap: insert a gap between sus & res in the timeline (def: false)
266  # Proc mode: graph user processes and cpu usage in the timeline (def: false)
269  # Dev mode: graph source functions in the timeline (def: false)
287  # Callgraph: gather ftrace callgraph data on all timeline events (def: false)
302  # Override default timeline entries:
303  # Do not use the internal default functions for timeline entries (def: false)
305  override-timeline-functions: true
307  # Override default dev timeline entries:
308  # Do not use the internal default functions for dev timeline entries (def: false)
310  override-dev-timeline-functions: true
328  timeline where device callbacks don't appear. For instance, in suspend_prepare
330  in the timeline to show you where the time is going. These calls should fill
331  the timeline with contiguous data so that most kernel execution is covered.
333  It is possible to add new function calls to the timeline by adding them to
334  the config. It's also possible to copy the internal timeline functions into
339  Use the override-timeline-functions option if you only want to use your
348  For a full example config, see config/custom-timeline-functions.cfg. It pulls
349  all the internal timeline functions into the config and allows you to edit
366     format: The format to display the data on the timeline in. Use braces to
371     color: The color of the entry block in the timeline. The default color is
382  Here is a full example entry. It displays cpu resume calls in the timeline
393  execution within the timeline entries.
396  timeline. However, if a function call is not within a main timeline event,
407  It is possible to add new function calls to the dev timeline by adding them
408  to the config. It's also possible to copy the internal dev timeline
413  Use the override-dev-timeline-functions option if you only want to use your
423  For a full example config, see config/custom-timeline-functions.cfg. It pulls
424  all the internal dev timeline functions into the config and allows you to edit
428  ataN_port_reset in the timeline. This is where most of the SATA disk resume
450  sudo ./sleepgraph.py -config config/custom-timeline-functions.cfg -status
457     timeline data source: FTRACE (all trace events found)
459     verifying timeline kprobes work: