| Namhyung Kim | 14cbfbe | 2016-01-07 20:41:53 +0900 | [diff] [blame^] | 1 | For a higher level overview, try: perf report --sort comm,dso |
| 2 | Sample related events with: perf record -e '{cycles,instructions}:S' |
| 3 | Compare performance results with: perf diff [<old file> <new file>] |
| 4 | Boolean options have negative forms, e.g.: perf report --no-children |
| 5 | Customize output of perf script with: perf script -F event,ip,sym |
| 6 | Generate a script for your data: perf script -g <lang> |
| 7 | Save output of perf stat using: perf stat record <target workload> |
| 8 | Create an archive with symtabs to analyse on other machine: perf archive |
| 9 | Search options using a keyword: perf report -h <keyword> |
| 10 | Use parent filter to see specific call path: perf report -p <regex> |
| 11 | List events using substring match: perf list <keyword> |
| 12 | To see list of saved events and attributes: perf evlist -v |
| 13 | Use --symfs <dir> if your symbol files are in non-standard locations |
| 14 | To see callchains in a more compact form: perf report -g folded |