| Hitoshi Mitake | 84c6f88 | 2010-02-04 16:08:15 +0900 | [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|trace} |
| 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 trace' shows raw lock events. |
| 24 | |
| 25 | 'perf lock report' reports statistical data. |
| 26 | |
| Marcin Slusarz | 9826e83 | 2011-02-22 21:53:12 +0100 | [diff] [blame^] | 27 | COMMON OPTIONS |
| 28 | -------------- |
| Shawn Bohrer | 4aace25 | 2010-11-30 19:57:14 -0600 | [diff] [blame] | 29 | |
| 30 | -i:: |
| 31 | --input=<file>:: |
| 32 | Input file name. |
| 33 | |
| 34 | -v:: |
| 35 | --verbose:: |
| 36 | Be more verbose (show symbol address, etc). |
| 37 | |
| 38 | -D:: |
| 39 | --dump-raw-trace:: |
| 40 | Dump raw trace in ASCII. |
| 41 | |
| Marcin Slusarz | 9826e83 | 2011-02-22 21:53:12 +0100 | [diff] [blame^] | 42 | REPORT OPTIONS |
| 43 | -------------- |
| 44 | |
| 45 | -k:: |
| 46 | --key=<value>:: |
| 47 | Sorting key. Possible values: acquired (default), contended, |
| 48 | wait_total, wait_max, wait_min. |
| 49 | |
| Hitoshi Mitake | 84c6f88 | 2010-02-04 16:08:15 +0900 | [diff] [blame] | 50 | SEE ALSO |
| 51 | -------- |
| 52 | linkperf:perf[1] |