Lines Matching +full:run +full:- +full:time
8 pm-graph: suspend/resume/boot timing analysis tools
11 …Home Page: https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/overvi…
13 Report bugs/issues at bugzilla.kernel.org Tools/pm-graph
14 - https://bugzilla.kernel.org/buglist.cgi?component=pm-graph&product=Tools
17 - Getting Started:
20 - Feature Summary:
21 https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/features.html
23 - upstream version in git:
24 git clone https://github.com/intel/pm-graph/
27 - Overview
28 - Setup
29 - Usage
30 - Basic Usage
31 - Dev Mode Usage
32 - Proc Mode Usage
33 - Endurance Testing
34 - Usage Examples
35 - Configuration Files
36 - Usage Examples
37 - Config File Options
38 - Custom Timeline Entries
39 - Adding/Editing Timeline Functions
40 - Adding/Editing Dev Timeline Source Functions
41 - Verifying your Custom Functions
42 - Testing on consumer linux Operating Systems
43 - Android
45 ------------------------------------------------------------------
47 ------------------------------------------------------------------
50 their linux stack's suspend/resume & boot time. Using a kernel image built
54 and kernel processes are taking the most time in suspend/resume & boot.
56 ------------------------------------------------------------------
58 ------------------------------------------------------------------
61 - runs with python2 or python3, choice is made by /usr/bin/python link
62 - python
63 - python-configparser (for python2 sleepgraph)
64 - python-requests (for stresstester.py)
65 - linux-tools-common (for turbostat usage in sleepgraph)
68 sudo apt-get install python python-configparser python-requests linux-tools-common
71 sudo dnf install python python-configparser python-requests linux-tools-common
75 $> git clone http://github.com/intel/pm-graph.git
76 $> cd pm-graph
97 (kernel/pre-3.15/enable_trace_events_suspend_resume.patch)
98 (kernel/pre-3.15/enable_trace_events_device_pm_callback.patch)
105 If you're using a kernel older than 3.11-rc2, the following simple
113 (kernel/pre-3.11-rc2/enable_ftrace_in_suspendresume.patch)
117 ------------------------------------------------------------------
119 ------------------------------------------------------------------
128 %> sudo ./sleepgraph.py -modes
133 %> sudo ./sleepgraph.py -m mem -rtcwake 15
137 %> sudo ./sleepgraph.py -config config/suspend.cfg
141 files in subdirectory: suspend-mmddyy-HHMMSS. The ftrace file can
165 The timeline will be much larger if run with dev mode, so it can be useful
166 to set the -mindev option to clip out any device blocks that are too small
167 to see easily. The following command will give a nice dev mode run:
169 %> sudo ./sleepgraph.py -m mem -rtcwake 15 -mindev 1 -dev
173 %> sudo ./sleepgraph.py -config config/suspend-dev.cfg
187 can also be useful to run in x2 mode with an x2 delay, this way you can
191 The command can be run like this:
193 %> sudo ./sleepgraph.py -m mem -rtcwake 15 -x2 -x2delay 1000 -predelay 1000 -postdelay 1000 -proc
197 %> sudo ./sleepgraph.py -config config/suspend-proc.cfg
199 ------------------------------------------------------------------
201 ------------------------------------------------------------------
203 The best way to gauge the health of a system is to run a series of
205 accomplished with sleepgraph's -multi argument. You specify two numbers: the
206 number of tests to run OR the duration in days, hours, or minutes, and the
207 delay in seconds between them. For instance, -multi 20 5: execute 20 tests with
208 a 5 second delay between each, or -multi 24h 0: execute tests over a 24 hour
216 summary-issue.html and summary-devices.html files include data taken from
219 suspend-xN-{date}-{time}:
221 summary-issues.html
222 summary-devices.html
223 suspend-{date}-{time} (1)
224 suspend-{date}-{time} (2)
229 -m mode
232 -rtcwake t
235 -gzip (optional)
239 -dev (optional)
242 -multi n d
244 created in a new subdirectory: suspend-xN-{date}-{time}. When the multitest
245 run is done, the -summary command is called automatically to create summary
246 html files for all the data (unless you use -skiphtml). -skiphtml will
248 can then run the tool again at a later time with -summary and -genhtml to
251 -skiphtml (optional)
252 Run the test and capture the trace logs, but skip the timeline and summary
254 copy the data to a faster host machine and run -summary -genhtml to
259 -summary indir
260 Generate or regenerate the summary for a -multi test run. Creates three
261 files: summary.html, summary-issues.html, and summary-devices.html in the
263 by kernel/host/mode, and links to the test html files. summary-issues.html
265 summary-devices.html is a list of devices and times from all the tests.
267 -genhtml
268 Used with -summary to regenerate any missing html timelines from their
269 dmesg and ftrace logs. This will require a significant amount of time if
277 %> sudo ./sleepgraph.py -m mem -rtcwake 10 -dev -gzip -multi 2000 0
281 %> sudo ./sleepgraph.py -m mem -rtcwake 10 -dev -gzip -multi 2000 0 -skiphtml
285 depending on whether you used the -skiphtml option. The root folder contains
290 %> cd suspend-x2000-{date}-{time}
291 %> sleepgraph.py -summary .
293 or if you need to generate the html timelines you can use -genhtml
295 %> cd suspend-xN-{date}-{time}
296 %> sleepgraph.py -summary . -genhtml
298 ------------------------------------------------------------------
300 ------------------------------------------------------------------
312 config/suspend-dev.cfg
313 config/freeze-dev.cfg
314 config/standby-dev.cfg
317 config/suspend-callgraph.cfg
318 config/freeze-callgraph.cfg
319 config/standby-callgraph.cfg
321 Sample proc mode x2 run using mem suspend
322 config/suspend-x2-proc.cfg
325 config/custom-timeline-functions.cfg
328 config/debug-serio-suspend.cfg
334 Run a simple mem suspend:
335 %> sudo ./sleepgraph.py -config config/suspend.cfg
337 Run a mem suspend with callgraph data:
338 %> sudo ./sleepgraph.py -config config/suspend-callgraph.cfg
340 Run a mem suspend with dev mode detail:
341 %> sudo ./sleepgraph.py -config config/suspend-dev.cfg
355 # Output Directory Format: {hostname}, {date}, {time} give current values
356 output-dir: suspend-{hostname}-{date}-{time}
376 # Suspend/Resume x2: run 2 suspend/resumes back to back (def: false)
379 # x2 Suspend Delay: time delay between the two test runs in ms (def: 0 ms)
394 # Expand Callgraph: pre-expand the callgraph treeviews in html (def: false)
409 override-timeline-functions: true
414 override-dev-timeline-functions: true
418 callloop-maxgap: 0.0001
422 callloop-maxlen: 0.005
424 ------------------------------------------------------------------
426 ------------------------------------------------------------------
434 in the timeline to show you where the time is going. These calls should fill
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
507 the functions that add a hardcoded time delay to the suspend/resume path.
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
533 time goes, so it can be helpful to see the low level call.
544 actually supports them. To do this, run the tool with your config file
545 and the -status option. The tool will go through all the kprobes (both
554 sudo ./sleepgraph.py -config config/custom-timeline-functions.cfg -status
586 ------------------------------------------------------------------
588 ------------------------------------------------------------------
593 The easiest way to execute on an android device is to run the android.sh
594 script on the device, then pull the ftrace log back to the host and run
601 host%> wget https://raw.githubusercontent.com/intel/pm-graph/master/tools/android.sh
607 [check whether the tool will run on your device]
613 kernel : 3.14.0-i386-dirty
629 ------------------------------------
631 ------------------------------------
633 kernel : 3.14.0-i386-dirty
638 ------------------------------------
647 # reconnect sometimes in order for the connection to work post-suspend
658 host%> sleepgraph.py -ftrace ftrace.txt