2009-09-11 12:12:54 +02:00
|
|
|
perf-sched(1)
|
|
|
|
|
==============
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
2009-09-13 16:51:04 +02:00
|
|
|
perf-sched - Tool to trace/measure scheduler properties (latencies)
|
2009-09-11 12:12:54 +02:00
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
|
|
|
|
[verse]
|
2009-09-13 16:51:04 +02:00
|
|
|
'perf sched' {record|latency|replay|trace}
|
2009-09-11 12:12:54 +02:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2010-03-31 11:31:00 -07:00
|
|
|
There are four variants of perf sched:
|
2009-09-13 16:51:04 +02:00
|
|
|
|
|
|
|
|
'perf sched record <command>' to record the scheduling events
|
|
|
|
|
of an arbitrary workload.
|
|
|
|
|
|
|
|
|
|
'perf sched latency' to report the per task scheduling latencies
|
|
|
|
|
and other scheduling properties of the workload.
|
|
|
|
|
|
|
|
|
|
'perf sched trace' to see a detailed trace of the workload that
|
|
|
|
|
was recorded.
|
|
|
|
|
|
|
|
|
|
'perf sched replay' to simulate the workload that was recorded
|
|
|
|
|
via perf sched record. (this is done by starting up mockup threads
|
|
|
|
|
that mimic the workload based on the events in the trace. These
|
|
|
|
|
threads can then replay the timings (CPU runtime and sleep patterns)
|
2010-03-31 11:31:00 -07:00
|
|
|
of the workload as it occurred when it was recorded - and can repeat
|
2009-09-13 16:51:04 +02:00
|
|
|
it a number of times, measuring its performance.)
|
2009-09-11 12:12:54 +02:00
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
|
-------
|
|
|
|
|
-D::
|
|
|
|
|
--dump-raw-trace=::
|
|
|
|
|
Display verbose dump of the sched data.
|
|
|
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
linkperf:perf-record[1]
|
