blob: 8ff4df95695128259abbd60e111283770f3a4b76 [file] [log] [blame]
Ingo Molnar0a02ad92009-09-11 12:12:54 +02001perf-sched(1)
2==============
3
4NAME
5----
Ingo Molnarc13f0d32009-09-13 16:51:04 +02006perf-sched - Tool to trace/measure scheduler properties (latencies)
Ingo Molnar0a02ad92009-09-11 12:12:54 +02007
8SYNOPSIS
9--------
10[verse]
Jiri Olsae78cb362011-09-27 11:16:35 +020011'perf sched' {record|latency|map|replay|script}
Ingo Molnar0a02ad92009-09-11 12:12:54 +020012
13DESCRIPTION
14-----------
Shawn Bohrer1eacc942010-11-30 19:57:18 -060015There are five variants of perf sched:
Ingo Molnarc13f0d32009-09-13 16:51:04 +020016
17 'perf sched record <command>' to record the scheduling events
18 of an arbitrary workload.
19
20 'perf sched latency' to report the per task scheduling latencies
21 and other scheduling properties of the workload.
22
Jiri Olsae78cb362011-09-27 11:16:35 +020023 'perf sched script' to see a detailed trace of the workload that
24 was recorded (aliased to 'perf script' for now).
Ingo Molnarc13f0d32009-09-13 16:51:04 +020025
26 'perf sched replay' to simulate the workload that was recorded
27 via perf sched record. (this is done by starting up mockup threads
28 that mimic the workload based on the events in the trace. These
29 threads can then replay the timings (CPU runtime and sleep patterns)
Randy Dunlap854c5542010-03-31 11:31:00 -070030 of the workload as it occurred when it was recorded - and can repeat
Ingo Molnarc13f0d32009-09-13 16:51:04 +020031 it a number of times, measuring its performance.)
Ingo Molnar0a02ad92009-09-11 12:12:54 +020032
Shawn Bohrer1eacc942010-11-30 19:57:18 -060033 'perf sched map' to print a textual context-switching outline of
34 workload captured via perf sched record. Columns stand for
35 individual CPUs, and the two-letter shortcuts stand for tasks that
36 are running on a CPU. A '*' denotes the CPU that had the event, and
37 a dot signals an idle CPU.
38
Ingo Molnar0a02ad92009-09-11 12:12:54 +020039OPTIONS
40-------
Shawn Bohrer1eacc942010-11-30 19:57:18 -060041-i::
42--input=<file>::
Robert Richterefad1412011-12-07 10:02:54 +010043 Input file name. (default: perf.data unless stdin is a fifo)
Shawn Bohrer1eacc942010-11-30 19:57:18 -060044
45-v::
46--verbose::
47 Be more verbose. (show symbol address, etc)
48
Ingo Molnar0a02ad92009-09-11 12:12:54 +020049-D::
50--dump-raw-trace=::
51 Display verbose dump of the sched data.
52
53SEE ALSO
54--------
55linkperf:perf-record[1]