blob: 1ce79198997b00248c077a5ac46af22a0ab461fb [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]
Ingo Molnarc13f0d32009-09-13 16:51:04 +020011'perf sched' {record|latency|replay|trace}
Ingo Molnar0a02ad92009-09-11 12:12:54 +020012
13DESCRIPTION
14-----------
Ingo Molnarc13f0d32009-09-13 16:51:04 +020015There's four variants of perf sched:
16
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
23 'perf sched trace' to see a detailed trace of the workload that
24 was recorded.
25
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)
30 of the workload as it occured when it was recorded - and can repeat
31 it a number of times, measuring its performance.)
Ingo Molnar0a02ad92009-09-11 12:12:54 +020032
33OPTIONS
34-------
35-D::
36--dump-raw-trace=::
37 Display verbose dump of the sched data.
38
39SEE ALSO
40--------
41linkperf:perf-record[1]