2009-09-11 12:12:54 +02:00
|
|
|
perf-sched(1)
|
2018-03-07 11:54:41 +01:00
|
|
|
=============
|
2009-09-11 12:12:54 +02:00
|
|
|
|
|
|
|
|
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]
|
2016-11-16 15:06:29 +09:00
|
|
|
'perf sched' {record|latency|map|replay|script|timehist}
|
2009-09-11 12:12:54 +02:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2016-11-16 15:06:29 +09:00
|
|
|
There are several 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.
|
|
|
|
|
|
2024-03-28 14:30:05 +05:30
|
|
|
Example usage:
|
|
|
|
|
perf sched record -- sleep 1
|
|
|
|
|
perf sched latency
|
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------------------------------------------------------------------
|
|
|
|
|
Task | Runtime ms | Count | Avg delay ms | Max delay ms | Max delay start | Max delay end |
|
|
|
|
|
-------------------------------------------------------------------------------------------------------------------------------------------
|
|
|
|
|
perf:(2) | 2.804 ms | 66 | avg: 0.524 ms | max: 1.069 ms | max start: 254752.314960 s | max end: 254752.316029 s
|
|
|
|
|
NetworkManager:1343 | 0.372 ms | 13 | avg: 0.008 ms | max: 0.013 ms | max start: 254751.551153 s | max end: 254751.551166 s
|
|
|
|
|
kworker/1:2-xfs:4649 | 0.012 ms | 1 | avg: 0.008 ms | max: 0.008 ms | max start: 254751.519807 s | max end: 254751.519815 s
|
|
|
|
|
kworker/3:1-xfs:388 | 0.011 ms | 1 | avg: 0.006 ms | max: 0.006 ms | max start: 254751.519809 s | max end: 254751.519815 s
|
|
|
|
|
sleep:147736 | 0.938 ms | 3 | avg: 0.006 ms | max: 0.007 ms | max start: 254751.313817 s | max end: 254751.313824 s
|
|
|
|
|
|
|
|
|
|
It shows Runtime(time that a task spent actually running on the CPU),
|
|
|
|
|
Count(number of times a delay was calculated) and delay(time that a
|
|
|
|
|
task was ready to run but was kept waiting).
|
|
|
|
|
|
|
|
|
|
Tasks with the same command name are merged and the merge count is
|
|
|
|
|
given within (), However if -p option is used, pid is mentioned.
|
|
|
|
|
|
2011-09-27 11:16:35 +02:00
|
|
|
'perf sched script' to see a detailed trace of the workload that
|
|
|
|
|
was recorded (aliased to 'perf script' for now).
|
2009-09-13 16:51:04 +02:00
|
|
|
|
|
|
|
|
'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
|
|
|
|
2010-11-30 19:57:18 -06:00
|
|
|
'perf sched map' to print a textual context-switching outline of
|
|
|
|
|
workload captured via perf sched record. Columns stand for
|
|
|
|
|
individual CPUs, and the two-letter shortcuts stand for tasks that
|
|
|
|
|
are running on a CPU. A '*' denotes the CPU that had the event, and
|
|
|
|
|
a dot signals an idle CPU.
|
|
|
|
|
|
2016-11-16 15:06:29 +09:00
|
|
|
'perf sched timehist' provides an analysis of scheduling events.
|
|
|
|
|
|
|
|
|
|
Example usage:
|
|
|
|
|
perf sched record -- sleep 1
|
|
|
|
|
perf sched timehist
|
|
|
|
|
|
|
|
|
|
By default it shows the individual schedule events, including the wait
|
|
|
|
|
time (time between sched-out and next sched-in events for the task), the
|
2024-06-18 11:03:39 +02:00
|
|
|
task scheduling delay (time between runnable and actually running) and
|
|
|
|
|
run time for the task:
|
2016-11-16 15:06:29 +09:00
|
|
|
|
|
|
|
|
time cpu task name wait time sch delay run time
|
|
|
|
|
[tid/pid] (msec) (msec) (msec)
|
|
|
|
|
-------------- ------ -------------------- --------- --------- ---------
|
|
|
|
|
79371.874569 [0011] gcc[31949] 0.014 0.000 1.148
|
|
|
|
|
79371.874591 [0010] gcc[31951] 0.000 0.000 0.024
|
|
|
|
|
79371.874603 [0010] migration/10[59] 3.350 0.004 0.011
|
|
|
|
|
79371.874604 [0011] <idle> 1.148 0.000 0.035
|
|
|
|
|
79371.874723 [0005] <idle> 0.016 0.000 1.383
|
|
|
|
|
79371.874746 [0005] gcc[31949] 0.153 0.078 0.022
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
Times are in msec.usec.
|
|
|
|
|
|
2009-09-11 12:12:54 +02:00
|
|
|
OPTIONS
|
|
|
|
|
-------
|
2010-11-30 19:57:18 -06:00
|
|
|
-i::
|
|
|
|
|
--input=<file>::
|
2011-12-07 10:02:54 +01:00
|
|
|
Input file name. (default: perf.data unless stdin is a fifo)
|
2010-11-30 19:57:18 -06:00
|
|
|
|
|
|
|
|
-v::
|
|
|
|
|
--verbose::
|
|
|
|
|
Be more verbose. (show symbol address, etc)
|
|
|
|
|
|
2009-09-11 12:12:54 +02:00
|
|
|
-D::
|
|
|
|
|
--dump-raw-trace=::
|
|
|
|
|
Display verbose dump of the sched data.
|
|
|
|
|
|
2017-11-16 23:26:05 +09:00
|
|
|
-f::
|
|
|
|
|
--force::
|
|
|
|
|
Don't complain, do it.
|
|
|
|
|
|
2024-03-28 14:30:05 +05:30
|
|
|
OPTIONS for 'perf sched latency'
|
|
|
|
|
-------------------------------
|
|
|
|
|
|
|
|
|
|
-C::
|
|
|
|
|
--CPU <n>::
|
|
|
|
|
CPU to profile on.
|
|
|
|
|
|
|
|
|
|
-p::
|
|
|
|
|
--pids::
|
|
|
|
|
latency stats per pid instead of per command name.
|
|
|
|
|
|
|
|
|
|
-s::
|
|
|
|
|
--sort <key[,key2...]>::
|
|
|
|
|
sort by key(s): runtime, switch, avg, max
|
|
|
|
|
by default it's sorted by "avg ,max ,switch ,runtime".
|
|
|
|
|
|
2016-04-12 15:29:26 +02:00
|
|
|
OPTIONS for 'perf sched map'
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
--compact::
|
|
|
|
|
Show only CPUs with activity. Helps visualizing on high core
|
|
|
|
|
count systems.
|
|
|
|
|
|
2016-04-12 15:29:31 +02:00
|
|
|
--cpus::
|
|
|
|
|
Show just entries with activities for the given CPUs.
|
|
|
|
|
|
2016-04-12 15:29:30 +02:00
|
|
|
--color-cpus::
|
|
|
|
|
Highlight the given cpus.
|
|
|
|
|
|
2016-04-12 15:29:29 +02:00
|
|
|
--color-pids::
|
|
|
|
|
Highlight the given pids.
|
|
|
|
|
|
2024-07-07 23:57:14 +05:30
|
|
|
--task-name <task>::
|
2024-07-07 23:57:15 +05:30
|
|
|
Map output only for the given task name(s). Separate the
|
|
|
|
|
task names with a comma (without whitespace). The sched-out
|
2024-07-07 23:57:14 +05:30
|
|
|
time is printed and is represented by '*-' for the given
|
2024-07-07 23:57:15 +05:30
|
|
|
task name(s).
|
2024-07-07 23:57:14 +05:30
|
|
|
('-' indicates other tasks while '.' is idle).
|
|
|
|
|
|
2024-07-07 23:57:16 +05:30
|
|
|
--fuzzy-name::
|
|
|
|
|
Given task name(s) can be partially matched (fuzzy matching).
|
|
|
|
|
|
2016-11-16 15:06:29 +09:00
|
|
|
OPTIONS for 'perf sched timehist'
|
|
|
|
|
---------------------------------
|
|
|
|
|
-k::
|
|
|
|
|
--vmlinux=<file>::
|
|
|
|
|
vmlinux pathname
|
|
|
|
|
|
|
|
|
|
--kallsyms=<file>::
|
|
|
|
|
kallsyms pathname
|
|
|
|
|
|
2016-11-16 15:06:32 +09:00
|
|
|
-g::
|
2018-04-10 23:35:39 +09:00
|
|
|
--call-graph::
|
|
|
|
|
Display call chains if present (default on).
|
2016-11-16 15:06:32 +09:00
|
|
|
|
|
|
|
|
--max-stack::
|
|
|
|
|
Maximum number of functions to display in backtrace, default 5.
|
|
|
|
|
|
2019-12-04 10:39:25 -07:00
|
|
|
-C=::
|
|
|
|
|
--cpu=::
|
|
|
|
|
Only show events for the given CPU(s) (comma separated list).
|
|
|
|
|
|
2017-09-01 10:49:12 -07:00
|
|
|
-p=::
|
|
|
|
|
--pid=::
|
|
|
|
|
Only show events for given process ID (comma separated list).
|
|
|
|
|
|
|
|
|
|
-t=::
|
|
|
|
|
--tid=::
|
|
|
|
|
Only show events for given thread ID (comma separated list).
|
|
|
|
|
|
2016-11-16 15:06:29 +09:00
|
|
|
-s::
|
|
|
|
|
--summary::
|
|
|
|
|
Show only a summary of scheduling by thread with min, max, and average
|
|
|
|
|
run times (in sec) and relative stddev.
|
|
|
|
|
|
|
|
|
|
-S::
|
|
|
|
|
--with-summary::
|
|
|
|
|
Show all scheduling events followed by a summary by thread with min,
|
|
|
|
|
max, and average run times (in sec) and relative stddev.
|
|
|
|
|
|
|
|
|
|
--symfs=<directory>::
|
|
|
|
|
Look for files with symbols relative to this directory.
|
|
|
|
|
|
2016-11-16 15:06:33 +09:00
|
|
|
-V::
|
|
|
|
|
--cpu-visual::
|
|
|
|
|
Show visual aid for sched switches by CPU: 'i' marks idle time,
|
|
|
|
|
's' are scheduler events.
|
|
|
|
|
|
2016-11-16 15:06:31 +09:00
|
|
|
-w::
|
|
|
|
|
--wakeups::
|
|
|
|
|
Show wakeup events.
|
|
|
|
|
|
2016-11-25 09:28:41 -07:00
|
|
|
-M::
|
|
|
|
|
--migrations::
|
|
|
|
|
Show migration events.
|
|
|
|
|
|
2017-03-14 01:56:29 +00:00
|
|
|
-n::
|
|
|
|
|
--next::
|
|
|
|
|
Show next task.
|
|
|
|
|
|
2016-12-08 23:47:54 +09:00
|
|
|
-I::
|
|
|
|
|
--idle-hist::
|
|
|
|
|
Show idle-related events only.
|
|
|
|
|
|
2016-11-29 10:15:44 -07:00
|
|
|
--time::
|
|
|
|
|
Only analyze samples within given time window: <start>,<stop>. Times
|
|
|
|
|
have the format seconds.microseconds. If start is not given (i.e., time
|
|
|
|
|
string is ',x.y') then analysis starts at the beginning of the file. If
|
|
|
|
|
stop time is not given (i.e, time string is 'x.y,') then analysis goes
|
|
|
|
|
to end of file.
|
|
|
|
|
|
2017-01-13 19:45:22 +09:00
|
|
|
--state::
|
|
|
|
|
Show task state when it switched out.
|
2016-11-29 10:15:44 -07:00
|
|
|
|
perf sched timehist: Add --show-prio option
The --show-prio option is used to display the priority of task.
It is disabled by default, which is consistent with original behavior.
The display format is xxx (priority does not change during task running)
or xxx->yyy (priority changes during task running)
Testcase:
# perf sched record nice -n 9 true
[ perf record: Woken up 0 times to write data ]
[ perf record: Captured and wrote 0.497 MB perf.data ]
# perf sched timehist -h
Usage: perf sched timehist [<options>]
-C, --cpu <cpu> list of cpus to profile
-D, --dump-raw-trace dump raw trace in ASCII
-f, --force don't complain, do it
-g, --call-graph Display call chains if present (default on)
-I, --idle-hist Show idle events only
-i, --input <file> input file name
-k, --vmlinux <file> vmlinux pathname
-M, --migrations Show migration events
-n, --next Show next task
-p, --pid <pid[,pid...]>
analyze events only for given process id(s)
-s, --summary Show only syscall summary with statistics
-S, --with-summary Show all syscalls and summary with statistics
-t, --tid <tid[,tid...]>
analyze events only for given thread id(s)
-V, --cpu-visual Add CPU visual
-v, --verbose be more verbose (show symbol address, etc)
-w, --wakeups Show wakeup events
--kallsyms <file>
kallsyms pathname
--max-stack <n> Maximum number of functions to display backtrace.
--show-prio Show task priority
--state Show task state when sched-out
--symfs <directory>
Look for files with symbols relative to this directory
--time <str> Time span for analysis (start,stop)
# perf sched timehist
Samples of sched_switch event do not have callchains.
time cpu task name wait time sch delay run time
[tid/pid] (msec) (msec) (msec)
--------------- ------ ------------------------------ --------- --------- ---------
23952.006537 [0000] perf[534] 0.000 0.000 0.000
23952.006593 [0000] migration/0[19] 0.000 0.014 0.056
23952.006899 [0001] perf[534] 0.000 0.000 0.000
23952.006947 [0001] migration/1[22] 0.000 0.015 0.047
23952.007138 [0002] perf[534] 0.000 0.000 0.000
<SNIP>
# perf sched timehist --show-prio
Samples of sched_switch event do not have callchains.
time cpu task name prio wait time sch delay run time
[tid/pid] (msec) (msec) (msec)
--------------- ------ ------------------------------ -------- --------- --------- ---------
23952.006537 [0000] perf[534] 120 0.000 0.000 0.000
23952.006593 [0000] migration/0[19] 0 0.000 0.014 0.056
23952.006899 [0001] perf[534] 120 0.000 0.000 0.000
<SNIP>
23952.034843 [0003] nice[535] 120->129 0.189 0.024 23.314
<SNIP>
23952.053838 [0005] rcu_preempt[16] 120 3.993 0.000 0.023
23952.053990 [0005] <idle> 120 0.023 0.023 0.152
23952.054137 [0006] <idle> 120 1.427 1.427 17.855
23952.054278 [0007] <idle> 120 0.506 0.506 1.650
Signed-off-by: Yang Jihong <yangjihong@bytedance.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: James Clark <james.clark@arm.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20240819033016.2427235-2-yangjihong@bytedance.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2024-08-19 11:30:15 +08:00
|
|
|
--show-prio::
|
|
|
|
|
Show task priority.
|
|
|
|
|
|
perf sched timehist: Add --prio option
The --prio option is used to only show events for the given task priority(ies).
The default is to show events for all priority tasks, which is consistent with
the previous behavior.
Testcase:
# perf sched record nice -n 9 perf bench sched messaging -l 10000
# Running 'sched/messaging' benchmark:
# 20 sender and receiver processes per group
# 10 groups == 400 processes run
Total time: 3.435 [sec]
[ perf record: Woken up 270 times to write data ]
[ perf record: Captured and wrote 618.688 MB perf.data (5729036 samples) ]
# perf sched timehist -h
Usage: perf sched timehist [<options>]
-C, --cpu <cpu> list of cpus to profile
-D, --dump-raw-trace dump raw trace in ASCII
-f, --force don't complain, do it
-g, --call-graph Display call chains if present (default on)
-I, --idle-hist Show idle events only
-i, --input <file> input file name
-k, --vmlinux <file> vmlinux pathname
-M, --migrations Show migration events
-n, --next Show next task
-p, --pid <pid[,pid...]>
analyze events only for given process id(s)
-s, --summary Show only syscall summary with statistics
-S, --with-summary Show all syscalls and summary with statistics
-t, --tid <tid[,tid...]>
analyze events only for given thread id(s)
-V, --cpu-visual Add CPU visual
-v, --verbose be more verbose (show symbol address, etc)
-w, --wakeups Show wakeup events
--kallsyms <file>
kallsyms pathname
--max-stack <n> Maximum number of functions to display backtrace.
--prio <prio> analyze events only for given task priority(ies)
--show-prio Show task priority
--state Show task state when sched-out
--symfs <directory>
Look for files with symbols relative to this directory
--time <str> Time span for analysis (start,stop)
# perf sched timehist --prio 140
Samples of sched_switch event do not have callchains.
Invalid prio string
# perf sched timehist --show-prio --prio 129
Samples of sched_switch event do not have callchains.
time cpu task name prio wait time sch delay run time
[tid/pid] (msec) (msec) (msec)
--------------- ------ ------------------------------ -------- --------- --------- ---------
2090450.765421 [0002] sched-messaging[1229618] 129 0.000 0.000 0.029
2090450.765445 [0007] sched-messaging[1229616] 129 0.000 0.062 0.043
2090450.765448 [0014] sched-messaging[1229619] 129 0.000 0.000 0.032
2090450.765478 [0013] sched-messaging[1229617] 129 0.000 0.065 0.048
2090450.765503 [0014] sched-messaging[1229622] 129 0.000 0.000 0.017
2090450.765550 [0002] sched-messaging[1229624] 129 0.000 0.000 0.021
2090450.765562 [0007] sched-messaging[1229621] 129 0.000 0.071 0.028
2090450.765570 [0005] sched-messaging[1229620] 129 0.000 0.064 0.066
2090450.765583 [0001] sched-messaging[1229625] 129 0.000 0.001 0.031
2090450.765595 [0013] sched-messaging[1229623] 129 0.000 0.060 0.028
2090450.765637 [0014] sched-messaging[1229628] 129 0.000 0.000 0.019
2090450.765665 [0007] sched-messaging[1229627] 129 0.000 0.038 0.030
<SNIP>
# perf sched timehist --show-prio --prio 0,120-129
Samples of sched_switch event do not have callchains.
time cpu task name prio wait time sch delay run time
[tid/pid] (msec) (msec) (msec)
--------------- ------ ------------------------------ -------- --------- --------- ---------
2090450.763231 [0000] perf[1229608] 120 0.000 0.000 0.000
2090450.763235 [0000] migration/0[15] 0 0.000 0.001 0.003
2090450.763263 [0001] perf[1229608] 120 0.000 0.000 0.000
2090450.763268 [0001] migration/1[21] 0 0.000 0.001 0.004
2090450.763302 [0002] perf[1229608] 120 0.000 0.000 0.000
2090450.763309 [0002] migration/2[27] 0 0.000 0.001 0.007
2090450.763338 [0003] perf[1229608] 120 0.000 0.000 0.000
2090450.763343 [0003] migration/3[33] 0 0.000 0.001 0.004
2090450.763459 [0004] perf[1229608] 120 0.000 0.000 0.000
2090450.763469 [0004] migration/4[39] 0 0.000 0.002 0.010
2090450.763496 [0005] perf[1229608] 120 0.000 0.000 0.000
2090450.763501 [0005] migration/5[45] 0 0.000 0.001 0.004
2090450.763613 [0006] perf[1229608] 120 0.000 0.000 0.000
2090450.763622 [0006] migration/6[51] 0 0.000 0.001 0.008
2090450.763652 [0007] perf[1229608] 120 0.000 0.000 0.000
2090450.763660 [0007] migration/7[57] 0 0.000 0.001 0.008
<SNIP>
2090450.765665 [0001] <idle> 120 0.031 0.031 0.081
2090450.765665 [0007] sched-messaging[1229627] 129 0.000 0.038 0.030
2090450.765667 [0000] s1-perf[8235/7168] 120 0.008 0.000 0.004
2090450.765684 [0013] <idle> 120 0.028 0.028 0.088
2090450.765685 [0001] sched-messaging[1229630] 129 0.000 0.001 0.020
2090450.765688 [0000] <idle> 120 0.004 0.004 0.020
2090450.765689 [0002] <idle> 120 0.021 0.021 0.138
2090450.765691 [0005] sched-messaging[1229626] 129 0.000 0.085 0.029
Signed-off-by: Yang Jihong <yangjihong@bytedance.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: James Clark <james.clark@arm.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20240819033016.2427235-3-yangjihong@bytedance.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2024-08-19 11:30:16 +08:00
|
|
|
--prio::
|
|
|
|
|
Only show events for given task priority(ies). Multiple priorities can be
|
|
|
|
|
provided as a comma-separated list with no spaces: 0,120. Ranges of
|
|
|
|
|
priorities are specified with -: 120-129. A combination of both can also be
|
|
|
|
|
provided: 0,120-129.
|
|
|
|
|
|
2024-10-04 22:37:56 +05:30
|
|
|
-P::
|
|
|
|
|
--pre-migrations::
|
|
|
|
|
Show pre-migration wait time. pre-migration wait time is the time spent
|
|
|
|
|
by a task waiting on a runqueue but not getting the chance to run there
|
|
|
|
|
and is migrated to a different runqueue where it is finally run. This
|
|
|
|
|
time between sched_wakeup and migrate_task is the pre-migration wait
|
|
|
|
|
time.
|
|
|
|
|
|
perf sched replay: Fix -r/--repeat command line option for infinity
Currently, the -r/--repeat option accepts values from 0 and complains
for -1. The help section specifies:
-r, --repeat <n> repeat the workload replay N times (-1: infinite)
The -r -1 option raises an error because replay_repeat is defined as
an unsigned int.
In the current implementation, the workload is repeated n times when
-r <n> is used, except when n is 0.
When -r is set to 0, the workload is also repeated once. This happens
because when -r=0, the run_one_test function is not called. (Note that
mutex unlocking, which is essential for child threads spawned to emulate
the workload, happens in run_one_test.) However, mutex unlocking is
still performed in the destroy_tasks function. Thus, -r=0 results in the
workload running once coincidentally.
To clarify and maintain the existing logic for -r >= 1 (which runs the
workload the specified number of times) and to fix the issue with infinite
runs, make -r=0 perform an infinite run.
Reviewed-by: James Clark <james.clark@arm.com>
Signed-off-by: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Cc: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Link: https://lore.kernel.org/r/20240628071821.15264-1-vineethr@linux.ibm.com
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
2024-06-28 12:48:21 +05:30
|
|
|
OPTIONS for 'perf sched replay'
|
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
|
|
-r::
|
|
|
|
|
--repeat <n>::
|
|
|
|
|
repeat the workload n times (0: infinite). Default is 10.
|
|
|
|
|
|
2009-09-11 12:12:54 +02:00
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
linkperf:perf-record[1]
|