| xj | b04a402 | 2021-11-25 15:01:52 +0800 | [diff] [blame] | 1 | perf-lock(1) |
| 2 | ============ |
| 3 | |
| 4 | NAME |
| 5 | ---- |
| 6 | perf-lock - Analyze lock events |
| 7 | |
| 8 | SYNOPSIS |
| 9 | -------- |
| 10 | [verse] |
| 11 | 'perf lock' {record|report|script|info} |
| 12 | |
| 13 | DESCRIPTION |
| 14 | ----------- |
| 15 | You can analyze various lock behaviours |
| 16 | and statistics with this 'perf lock' command. |
| 17 | |
| 18 | 'perf lock record <command>' records lock events |
| 19 | between start and end <command>. And this command |
| 20 | produces the file "perf.data" which contains tracing |
| 21 | results of lock events. |
| 22 | |
| 23 | 'perf lock report' reports statistical data. |
| 24 | |
| 25 | 'perf lock script' shows raw lock events. |
| 26 | |
| 27 | 'perf lock info' shows metadata like threads or addresses |
| 28 | of lock instances. |
| 29 | |
| 30 | COMMON OPTIONS |
| 31 | -------------- |
| 32 | |
| 33 | -i:: |
| 34 | --input=<file>:: |
| 35 | Input file name. (default: perf.data unless stdin is a fifo) |
| 36 | |
| 37 | -v:: |
| 38 | --verbose:: |
| 39 | Be more verbose (show symbol address, etc). |
| 40 | |
| 41 | -D:: |
| 42 | --dump-raw-trace:: |
| 43 | Dump raw trace in ASCII. |
| 44 | |
| 45 | -f:: |
| 46 | --force:: |
| 47 | Don't complan, do it. |
| 48 | |
| 49 | REPORT OPTIONS |
| 50 | -------------- |
| 51 | |
| 52 | -k:: |
| 53 | --key=<value>:: |
| 54 | Sorting key. Possible values: acquired (default), contended, |
| 55 | avg_wait, wait_total, wait_max, wait_min. |
| 56 | |
| 57 | INFO OPTIONS |
| 58 | ------------ |
| 59 | |
| 60 | -t:: |
| 61 | --threads:: |
| 62 | dump thread list in perf.data |
| 63 | |
| 64 | -m:: |
| 65 | --map:: |
| 66 | dump map of lock instances (address:name table) |
| 67 | |
| 68 | SEE ALSO |
| 69 | -------- |
| 70 | linkperf:perf[1] |