PERF-LOCK(1) | perf Manual | PERF-LOCK(1) |
NAME
perf-lock - Analyze lock events
SYNOPSIS
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>
--output=<file>
-v, --verbose
-q, --quiet
-D, --dump-raw-trace
-f, --force
--vmlinux=<file>
--kallsyms=<file>
REPORT OPTIONS
-k, --key=<value>
-F, --field=<value>
-c, --combine-locks
-t, --threads
$ 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
-E, --entries=<value>
INFO OPTIONS
-t, --threads
-m, --map
CONTENTION OPTIONS
-k, --key=<value>
-F, --field=<value>
-t, --threads
-b, --use-bpf
-a, --all-cpus
-C, --cpu=<value>
-p, --pid=<value>
--tid=<value>
-M, --map-nr-entries=<value>
--max-stack=<value>
--stack-skip=<value>
-E, --entries=<value>
-l, --lock-addr
-o, --lock-owner
-Y, --type-filter=<value>
Note that RW-variant of locks have :R and :W suffix. Names without the suffix are shortcuts for the both variants. Ex) rwsem = rwsem:R + rwsem:W.
-L, --lock-filter=<value>
-S, --callstack-filter=<value>
-x, --field-separator=<SEP>
--lock-cgroup
-G, --cgroup-filter=<value>
-J, --inject-delay=<time@function[1]>
The 'time' is specified in nsec but it can have a unit suffix. Available units are "ms", "us" and "ns". Currently it accepts up to 10ms of delays for safety reasons.
Note that it will busy-wait after it gets the lock. Delaying locks can have significant consequences including potential kernel crashes. Please use it at your own risk.
SEE ALSO
NOTES
- 1.
- time@function
2025-05-31 | perf |