528b9cab3b
The 'perf lock contention' processes the lock contention events and
displays the result like perf lock report. Right now, there's not
much difference between the two but the lock contention specific
features will come soon.
$ perf lock contention
contended total wait max wait avg wait type caller
238 1.41 ms 29.20 us 5.94 us spinlock update_blocked_averages+0x4c
1 902.08 us 902.08 us 902.08 us rwsem:R do_user_addr_fault+0x1dd
81 330.30 us 17.24 us 4.08 us spinlock _nohz_idle_balance+0x172
2 89.54 us 61.26 us 44.77 us spinlock do_anonymous_page+0x16d
24 78.36 us 12.27 us 3.27 us mutex pipe_read+0x56
2 71.58 us 59.56 us 35.79 us spinlock __handle_mm_fault+0x6aa
6 25.68 us 6.89 us 4.28 us spinlock do_idle+0x28d
1 18.46 us 18.46 us 18.46 us rtmutex exec_fw_cmd+0x21b
3 15.25 us 6.26 us 5.08 us spinlock tick_do_update_jiffies64+0x2c
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Cc: Boqun Feng <boqun.feng@gmail.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Waiman Long <longman@redhat.com>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20220725183124.368304-4-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
111 lines
2.6 KiB
Plaintext
111 lines
2.6 KiB
Plaintext
perf-lock(1)
|
|
============
|
|
|
|
NAME
|
|
----
|
|
perf-lock - Analyze lock events
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf lock' {record|report|script|info|contention}
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
You can analyze various lock behaviours
|
|
and statistics with this 'perf lock' command.
|
|
|
|
'perf lock record <command>' records lock events
|
|
between start and end <command>. And this command
|
|
produces the file "perf.data" which contains tracing
|
|
results of lock events.
|
|
|
|
'perf lock report' reports statistical data.
|
|
|
|
'perf lock script' shows raw lock events.
|
|
|
|
'perf lock info' shows metadata like threads or addresses
|
|
of lock instances.
|
|
|
|
'perf lock contention' shows contention statistics.
|
|
|
|
COMMON OPTIONS
|
|
--------------
|
|
|
|
-i::
|
|
--input=<file>::
|
|
Input file name. (default: perf.data unless stdin is a fifo)
|
|
|
|
-v::
|
|
--verbose::
|
|
Be more verbose (show symbol address, etc).
|
|
|
|
-D::
|
|
--dump-raw-trace::
|
|
Dump raw trace in ASCII.
|
|
|
|
-f::
|
|
--force::
|
|
Don't complain, do it.
|
|
|
|
--vmlinux=<file>::
|
|
vmlinux pathname
|
|
|
|
--kallsyms=<file>::
|
|
kallsyms pathname
|
|
|
|
|
|
REPORT OPTIONS
|
|
--------------
|
|
|
|
-k::
|
|
--key=<value>::
|
|
Sorting key. Possible values: acquired (default), contended,
|
|
avg_wait, wait_total, wait_max, wait_min.
|
|
|
|
-F::
|
|
--field=<value>::
|
|
Output fields. By default it shows all the fields but users can
|
|
customize that using this. Possible values: acquired, contended,
|
|
avg_wait, wait_total, wait_max, wait_min.
|
|
|
|
-c::
|
|
--combine-locks::
|
|
Merge lock instances in the same class (based on name).
|
|
|
|
-t::
|
|
--threads::
|
|
The -t option is to show per-thread lock stat like below:
|
|
|
|
$ perf lock report -t -F acquired,contended,avg_wait
|
|
|
|
Name acquired contended avg wait (ns)
|
|
|
|
perf 240569 9 5784
|
|
swapper 106610 19 543
|
|
:15789 17370 2 14538
|
|
ContainerMgr 8981 6 874
|
|
sleep 5275 1 11281
|
|
ContainerThread 4416 4 944
|
|
RootPressureThr 3215 5 1215
|
|
rcu_preempt 2954 0 0
|
|
ContainerMgr 2560 0 0
|
|
unnamed 1873 0 0
|
|
EventManager_De 1845 1 636
|
|
futex-default-S 1609 0 0
|
|
|
|
INFO OPTIONS
|
|
------------
|
|
|
|
-t::
|
|
--threads::
|
|
dump thread list in perf.data
|
|
|
|
-m::
|
|
--map::
|
|
dump map of lock instances (address:name table)
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf[1]
|