Commit | Line | Data |
---|---|---|
133dc4c3 | 1 | perf-script(1) |
4778e0e8 | 2 | ============= |
0a02ad93 IM |
3 | |
4 | NAME | |
5 | ---- | |
133dc4c3 | 6 | perf-script - Read perf.data (created by perf record) and display trace output |
0a02ad93 IM |
7 | |
8 | SYNOPSIS | |
9 | -------- | |
10 | [verse] | |
133dc4c3 IM |
11 | 'perf script' [<options>] |
12 | 'perf script' [<options>] record <script> [<record-options>] <command> | |
13 | 'perf script' [<options>] report <script> [script-args] | |
14 | 'perf script' [<options>] <script> <required-script-args> [<record-options>] <command> | |
15 | 'perf script' [<options>] <top-script> [script-args] | |
0a02ad93 IM |
16 | |
17 | DESCRIPTION | |
18 | ----------- | |
19 | This command reads the input file and displays the trace recorded. | |
20 | ||
133dc4c3 | 21 | There are several variants of perf script: |
a6005123 | 22 | |
133dc4c3 | 23 | 'perf script' to see a detailed trace of the workload that was |
a6005123 TZ |
24 | recorded. |
25 | ||
cff68e58 TZ |
26 | You can also run a set of pre-canned scripts that aggregate and |
27 | summarize the raw trace data in various ways (the list of scripts is | |
133dc4c3 | 28 | available via 'perf script -l'). The following variants allow you to |
cff68e58 TZ |
29 | record and run those scripts: |
30 | ||
133dc4c3 IM |
31 | 'perf script record <script> <command>' to record the events required |
32 | for 'perf script report'. <script> is the name displayed in the | |
33 | output of 'perf script --list' i.e. the actual script name minus any | |
d3c4f798 TZ |
34 | language extension. If <command> is not specified, the events are |
35 | recorded using the -a (system-wide) 'perf record' option. | |
a6005123 | 36 | |
133dc4c3 | 37 | 'perf script report <script> [args]' to run and display the results |
d3c4f798 | 38 | of <script>. <script> is the name displayed in the output of 'perf |
5c64f99b | 39 | script --list' i.e. the actual script name minus any language |
133dc4c3 | 40 | extension. The perf.data output from a previous run of 'perf script |
a6005123 | 41 | record <script>' is used and should be present for this command to |
d3c4f798 TZ |
42 | succeed. [args] refers to the (mainly optional) args expected by |
43 | the script. | |
44 | ||
133dc4c3 | 45 | 'perf script <script> <required-script-args> <command>' to both |
d3c4f798 TZ |
46 | record the events required for <script> and to run the <script> |
47 | using 'live-mode' i.e. without writing anything to disk. <script> | |
133dc4c3 | 48 | is the name displayed in the output of 'perf script --list' i.e. the |
d3c4f798 TZ |
49 | actual script name minus any language extension. If <command> is |
50 | not specified, the events are recorded using the -a (system-wide) | |
51 | 'perf record' option. If <script> has any required args, they | |
52 | should be specified before <command>. This mode doesn't allow for | |
53 | optional script args to be specified; if optional script args are | |
133dc4c3 IM |
54 | desired, they can be specified using separate 'perf script record' |
55 | and 'perf script report' commands, with the stdout of the record step | |
d3c4f798 TZ |
56 | piped to the stdin of the report script, using the '-o -' and '-i -' |
57 | options of the corresponding commands. | |
58 | ||
133dc4c3 | 59 | 'perf script <top-script>' to both record the events required for |
d3c4f798 TZ |
60 | <top-script> and to run the <top-script> using 'live-mode' |
61 | i.e. without writing anything to disk. <top-script> is the name | |
133dc4c3 | 62 | displayed in the output of 'perf script --list' i.e. the actual |
d3c4f798 TZ |
63 | script name minus any language extension; a <top-script> is defined |
64 | as any script name ending with the string 'top'. | |
65 | ||
133dc4c3 | 66 | [<record-options>] can be passed to the record steps of 'perf script |
d3c4f798 | 67 | record' and 'live-mode' variants; this isn't possible however for |
133dc4c3 | 68 | <top-script> 'live-mode' or 'perf script report' variants. |
a6005123 | 69 | |
cff68e58 TZ |
70 | See the 'SEE ALSO' section for links to language-specific |
71 | information on how to write and run your own trace scripts. | |
72 | ||
0a02ad93 IM |
73 | OPTIONS |
74 | ------- | |
d3c4f798 TZ |
75 | <command>...:: |
76 | Any command you can specify in a shell. | |
77 | ||
0a02ad93 | 78 | -D:: |
5c64f99b | 79 | --dump-raw-trace=:: |
0a02ad93 IM |
80 | Display verbose dump of the trace data. |
81 | ||
57190e38 AH |
82 | --dump-unsorted-raw-trace=:: |
83 | Same as --dump-raw-trace but not sorted in time order. | |
84 | ||
a6005123 TZ |
85 | -L:: |
86 | --Latency=:: | |
87 | Show latency attributes (irqs/preemption disabled, etc). | |
88 | ||
89 | -l:: | |
90 | --list=:: | |
91 | Display a list of available trace scripts. | |
92 | ||
f526d68b | 93 | -s ['lang']:: |
89fbf0b8 TZ |
94 | --script=:: |
95 | Process trace data with the given script ([lang]:script[.ext]). | |
f526d68b TZ |
96 | If the string 'lang' is specified in place of a script name, a |
97 | list of supported languages will be displayed instead. | |
89fbf0b8 TZ |
98 | |
99 | -g:: | |
100 | --gen-script=:: | |
133dc4c3 | 101 | Generate perf-script.[ext] starter script for given language, |
89fbf0b8 TZ |
102 | using current perf.data. |
103 | ||
291961fc AH |
104 | --dlfilter=<file>:: |
105 | Filter sample events using the given shared object file. | |
106 | Refer linkperf:perf-dlfilter[1] | |
107 | ||
3d032a25 AH |
108 | --dlarg=<arg>:: |
109 | Pass 'arg' as an argument to the dlfilter. --dlarg may be repeated | |
110 | to add more arguments. | |
111 | ||
3e8e2263 | 112 | --list-dlfilters:: |
638e2b99 AH |
113 | Display a list of available dlfilters. Use with option -v (must come |
114 | before option --list-dlfilters) to show long descriptions. | |
115 | ||
d3c4f798 TZ |
116 | -a:: |
117 | Force system-wide collection. Scripts run without a <command> | |
118 | normally use -a by default, while scripts run with a <command> | |
119 | normally don't - this option allows the latter to be run in | |
120 | system-wide mode. | |
121 | ||
646420f1 SB |
122 | -i:: |
123 | --input=:: | |
efad1415 | 124 | Input file name. (default: perf.data unless stdin is a fifo) |
646420f1 SB |
125 | |
126 | -d:: | |
127 | --debug-mode:: | |
128 | Do various checks like samples ordering and lost events. | |
d3c4f798 | 129 | |
dc323ce8 | 130 | -F:: |
176fcc5c | 131 | --fields:: |
745f43e3 | 132 | Comma separated list of fields to print. Options are: |
af9eb56b | 133 | comm, tid, pid, time, cpu, event, trace, ip, sym, dso, dsoff, addr, symoff, |
6b9bae63 | 134 | srcline, period, iregs, uregs, brstack, brstacksym, flags, bpf-output, |
99417234 CD |
135 | brstackinsn, brstackinsnlen, brstackoff, callindent, insn, disasm, |
136 | insnlen, synth, phys_addr, metric, misc, srccode, ipc, data_page_size, | |
137 | code_page_size, ins_lat, machine_pid, vcpu, cgroup, retire_lat. | |
138 | ||
47e78084 | 139 | Field list can be prepended with the type, trace, sw or hw, |
1424dc96 | 140 | to indicate to which event type the field list applies. |
cbb0bba9 | 141 | e.g., -F sw:comm,tid,time,ip,sym and -F trace:time,cpu,trace |
c0230b2b | 142 | |
cbb0bba9 | 143 | perf script -F <fields> |
176fcc5c ACM |
144 | |
145 | is equivalent to: | |
146 | ||
cbb0bba9 | 147 | perf script -F trace:<fields> -F sw:<fields> -F hw:<fields> |
48000a1a | 148 | |
176fcc5c ACM |
149 | i.e., the specified fields apply to all event types if the type string |
150 | is not given. | |
48000a1a | 151 | |
36ce5651 AK |
152 | In addition to overriding fields, it is also possible to add or remove |
153 | fields from the defaults. For example | |
154 | ||
155 | -F -cpu,+insn | |
156 | ||
157 | removes the cpu field and adds the insn field. Adding/removing fields | |
158 | cannot be mixed with normal overriding. | |
159 | ||
176fcc5c ACM |
160 | The arguments are processed in the order received. A later usage can |
161 | reset a prior request. e.g.: | |
48000a1a | 162 | |
cbb0bba9 | 163 | -F trace: -F comm,tid,time,ip,sym |
48000a1a | 164 | |
cbb0bba9 | 165 | The first -F suppresses trace events (field list is ""), but then the |
787bef17 | 166 | second invocation sets the fields to comm,tid,time,ip,sym. In this case a |
176fcc5c | 167 | warning is given to the user: |
48000a1a | 168 | |
176fcc5c | 169 | "Overriding previous field request for all events." |
48000a1a | 170 | |
96355f2c | 171 | Alternatively, consider the order: |
48000a1a | 172 | |
cbb0bba9 | 173 | -F comm,tid,time,ip,sym -F trace: |
48000a1a | 174 | |
cbb0bba9 | 175 | The first -F sets the fields for all events and the second -F |
176fcc5c ACM |
176 | suppresses trace events. The user is given a warning message about |
177 | the override, and the result of the above is that only S/W and H/W | |
178 | events are displayed with the given fields. | |
48000a1a | 179 | |
6ef362fd JO |
180 | It's possible tp add/remove fields only for specific event type: |
181 | ||
182 | -Fsw:-cpu,-period | |
183 | ||
184 | removes cpu and period from software events. | |
185 | ||
176fcc5c ACM |
186 | For the 'wildcard' option if a user selected field is invalid for an |
187 | event type, a message is displayed to the user that the option is | |
188 | ignored for that type. For example: | |
48000a1a | 189 | |
cbb0bba9 | 190 | $ perf script -F comm,tid,trace |
176fcc5c ACM |
191 | 'trace' not valid for hardware events. Ignoring. |
192 | 'trace' not valid for software events. Ignoring. | |
48000a1a | 193 | |
176fcc5c ACM |
194 | Alternatively, if the type is given an invalid field is specified it |
195 | is an error. For example: | |
48000a1a | 196 | |
cbb0bba9 | 197 | perf script -v -F sw:comm,tid,trace |
176fcc5c | 198 | 'trace' not valid for software events. |
48000a1a | 199 | |
176fcc5c | 200 | At this point usage is displayed, and perf-script exits. |
48000a1a | 201 | |
400ea6d3 | 202 | The flags field is synthesized and may have a value when Instruction |
26738598 | 203 | Trace decoding. The flags are "bcrosyiABExghDt" which stand for branch, |
400ea6d3 | 204 | call, return, conditional, system, asynchronous, interrupt, |
26738598 AH |
205 | transaction abort, trace begin, trace end, in transaction, VM-Entry, |
206 | VM-Exit, interrupt disabled and interrupt disable toggle respectively. | |
207 | Known combinations of flags are printed more nicely e.g. | |
055cd33d AH |
208 | "call" for "bc", "return" for "br", "jcc" for "bo", "jmp" for "b", |
209 | "int" for "bci", "iret" for "bri", "syscall" for "bcs", "sysret" for "brs", | |
210 | "async" for "by", "hw int" for "bcyi", "tx abrt" for "bA", "tr strt" for "bB", | |
f42907e8 | 211 | "tr end" for "bE", "vmentry" for "bcg", "vmexit" for "bch". |
26738598 AH |
212 | However the "x", "D" and "t" flags will be displayed separately in those |
213 | cases e.g. "jcc (xD)" for a condition branch within a transaction | |
214 | with interrupts disabled. Note, interrupts becoming disabled is "t", | |
215 | whereas interrupts becoming enabled is "Dt". | |
400ea6d3 | 216 | |
e216708d AH |
217 | The callindent field is synthesized and may have a value when |
218 | Instruction Trace decoding. For calls and returns, it will display the | |
219 | name of the symbol indented with spaces to reflect the stack depth. | |
220 | ||
99417234 CD |
221 | When doing instruction trace decoding, insn, disasm and insnlen give the |
222 | instruction bytes, disassembled instructions (requires libcapstone support) | |
223 | and the instruction length of the current instruction respectively. | |
224e2c97 | 224 | |
47e78084 AH |
225 | The synth field is used by synthesized events which may be created when |
226 | Instruction Trace decoding. | |
227 | ||
68fb45bf AH |
228 | The ipc (instructions per cycle) field is synthesized and may have a value when |
229 | Instruction Trace decoding. | |
230 | ||
e28fb159 | 231 | The machine_pid and vcpu fields are derived from data resulting from using |
0c39f147 | 232 | perf inject to insert a perf.data file recorded inside a virtual machine into |
e28fb159 AH |
233 | a perf.data file recorded on the host at the same time. |
234 | ||
3fd7a168 NK |
235 | The cgroup fields requires sample having the cgroup id which is saved |
236 | when "--all-cgroups" option is passed to 'perf record'. | |
237 | ||
176fcc5c | 238 | Finally, a user may not set fields to none for all event types. |
cbb0bba9 | 239 | i.e., -F "" is not allowed. |
176fcc5c | 240 | |
dc323ce8 | 241 | The brstack output includes branch related information with raw addresses using the |
48d02a1d | 242 | /v/v/v/v/cycles syntax in the following order: |
dc323ce8 SE |
243 | FROM: branch source instruction |
244 | TO : branch target instruction | |
245 | M/P/-: M=branch target mispredicted or branch direction was mispredicted, P=target predicted or direction predicted, -=not supported | |
246 | X/- : X=branch inside a transactional region, -=not in transaction region or not supported | |
247 | A/- : A=TSX abort entry, -=not aborted region or not supported | |
48d02a1d | 248 | cycles |
dc323ce8 SE |
249 | |
250 | The brstacksym is identical to brstack, except that the FROM and TO addresses are printed in a symbolic form if possible. | |
251 | ||
48d02a1d AK |
252 | When brstackinsn is specified the full assembler sequences of branch sequences for each sample |
253 | is printed. This is the full execution path leading to the sample. This is only supported when the | |
254 | sample was recorded with perf record -b or -j any. | |
255 | ||
6f680c6a KL |
256 | Use brstackinsnlen to print the brstackinsn lenght. For example, you |
257 | can’t know the next sequential instruction after an unconditional branch unless | |
258 | you calculate that based on its length. | |
259 | ||
106dacd8 MS |
260 | The brstackoff field will print an offset into a specific dso/binary. |
261 | ||
4bd1bef8 AK |
262 | With the metric option perf script can compute metrics for |
263 | sampling periods, similar to perf stat. This requires | |
7db7218a | 264 | specifying a group with multiple events defining metrics with the :S option |
4bd1bef8 | 265 | for perf record. perf will sample on the first event, and |
7db7218a | 266 | print computed metrics for all the events in the group. Please note |
4bd1bef8 | 267 | that the metric computed is averaged over the whole sampling |
7db7218a | 268 | period (since the last sample), not just for the sample point. |
4bd1bef8 | 269 | |
28a0b398 JO |
270 | For sample events it's possible to display misc field with -F +misc option, |
271 | following letters are displayed for each bit: | |
272 | ||
bf30cc18 AB |
273 | PERF_RECORD_MISC_KERNEL K |
274 | PERF_RECORD_MISC_USER U | |
275 | PERF_RECORD_MISC_HYPERVISOR H | |
276 | PERF_RECORD_MISC_GUEST_KERNEL G | |
277 | PERF_RECORD_MISC_GUEST_USER g | |
278 | PERF_RECORD_MISC_MMAP_DATA* M | |
279 | PERF_RECORD_MISC_COMM_EXEC E | |
280 | PERF_RECORD_MISC_SWITCH_OUT S | |
281 | PERF_RECORD_MISC_SWITCH_OUT_PREEMPT Sp | |
28a0b398 JO |
282 | |
283 | $ perf script -F +misc ... | |
284 | sched-messaging 1414 K 28690.636582: 4590 cycles ... | |
285 | sched-messaging 1407 U 28690.636600: 325620 cycles ... | |
286 | sched-messaging 1414 K 28690.636608: 19473 cycles ... | |
287 | misc field ___________/ | |
288 | ||
c0230b2b DA |
289 | -k:: |
290 | --vmlinux=<file>:: | |
291 | vmlinux pathname | |
292 | ||
293 | --kallsyms=<file>:: | |
294 | kallsyms pathname | |
295 | ||
296 | --symfs=<directory>:: | |
297 | Look for files with symbols relative to this directory. | |
298 | ||
299 | -G:: | |
300 | --hide-call-graph:: | |
301 | When printing symbols do not display call chain. | |
745f43e3 | 302 | |
64eff7d9 DA |
303 | --stop-bt:: |
304 | Stop display of callgraph at these symbols | |
305 | ||
c8e66720 | 306 | -C:: |
5d67be97 AB |
307 | --cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can |
308 | be provided as a comma-separated list with no space: 0,1. Ranges of | |
309 | CPUs are specified with -: 0-2. Default is to report samples on all | |
310 | CPUs. | |
311 | ||
e7984b7b DA |
312 | -c:: |
313 | --comms=:: | |
314 | Only display events for these comms. CSV that understands | |
315 | file://filename entries. | |
316 | ||
e03eaa40 DA |
317 | --pid=:: |
318 | Only show events for given process ID (comma separated list). | |
319 | ||
320 | --tid=:: | |
321 | Only show events for given thread ID (comma separated list). | |
322 | ||
fbe96f29 SE |
323 | -I:: |
324 | --show-info:: | |
325 | Display extended information about the perf.data file. This adds | |
326 | information which may be very large and thus may clutter the display. | |
327 | It currently includes: cpu and numa topology of the host system. | |
328 | It can only be used with the perf script report mode. | |
329 | ||
0bc8d205 AN |
330 | --show-kernel-path:: |
331 | Try to resolve the path of [kernel.kallsyms] | |
332 | ||
ad7ebb9a NK |
333 | --show-task-events |
334 | Display task related events (e.g. FORK, COMM, EXIT). | |
335 | ||
ba1ddf42 NK |
336 | --show-mmap-events |
337 | Display mmap related events (e.g. MMAP, MMAP2). | |
338 | ||
96a44bbc HB |
339 | --show-namespace-events |
340 | Display namespace events i.e. events of type PERF_RECORD_NAMESPACES. | |
341 | ||
7c14898b AH |
342 | --show-switch-events |
343 | Display context switch events i.e. events of type PERF_RECORD_SWITCH or | |
344 | PERF_RECORD_SWITCH_CPU_WIDE. | |
345 | ||
3d7c27b6 JO |
346 | --show-lost-events |
347 | Display lost events i.e. events of type PERF_RECORD_LOST. | |
348 | ||
3233b37a JO |
349 | --show-round-events |
350 | Display finished round events i.e. events of type PERF_RECORD_FINISHED_ROUND. | |
351 | ||
490c8cc9 JO |
352 | --show-bpf-events |
353 | Display bpf events i.e. events of type PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT. | |
354 | ||
160d4af9 NK |
355 | --show-cgroup-events |
356 | Display cgroup events i.e. events of type PERF_RECORD_CGROUP. | |
357 | ||
92ecf3a6 AH |
358 | --show-text-poke-events |
359 | Display text poke events i.e. events of type PERF_RECORD_TEXT_POKE and | |
360 | PERF_RECORD_KSYMBOL. | |
361 | ||
77e0070d MD |
362 | --demangle:: |
363 | Demangle symbol names to human readable form. It's enabled by default, | |
364 | disable with --no-demangle. | |
365 | ||
366 | --demangle-kernel:: | |
367 | Demangle kernel symbol names to human readable form (for C++ kernels). | |
368 | ||
e90debdd JO |
369 | --header |
370 | Show perf.data header. | |
371 | ||
372 | --header-only | |
373 | Show only perf.data header. | |
374 | ||
7a680eb9 AH |
375 | --itrace:: |
376 | Options for decoding instruction tracing data. The options are: | |
377 | ||
60b88d87 | 378 | include::itrace.txt[] |
7a680eb9 AH |
379 | |
380 | To disable decoding entirely, use --no-itrace. | |
381 | ||
a9710ba0 AK |
382 | --full-source-path:: |
383 | Show the full path for source files for srcline output. | |
384 | ||
6125cc8d ACM |
385 | --max-stack:: |
386 | Set the stack depth limit when parsing the callchain, anything | |
387 | beyond the specified depth will be ignored. This is a trade-off | |
388 | between information loss and faster processing especially for | |
389 | workloads that can have a very long callchain stack. | |
390 | Note that when using the --itrace option the synthesized callchain size | |
391 | will override this value if the synthesized callchain size is bigger. | |
392 | ||
fe176085 | 393 | Default: 127 |
6125cc8d | 394 | |
83e19860 AH |
395 | --ns:: |
396 | Use 9 decimal places when displaying time (i.e. show the nanoseconds) | |
397 | ||
e0be62cc JO |
398 | -f:: |
399 | --force:: | |
400 | Don't do ownership validation. | |
401 | ||
a91f4c47 DA |
402 | --time:: |
403 | Only analyze samples within given time window: <start>,<stop>. Times | |
0ccc69ba | 404 | have the format seconds.nanoseconds. If start is not given (i.e. time |
a91f4c47 | 405 | string is ',x.y') then analysis starts at the beginning of the file. If |
0ccc69ba | 406 | stop time is not given (i.e. time string is 'x.y,') then analysis goes |
a77a05e2 AH |
407 | to end of file. Multiple ranges can be separated by spaces, which |
408 | requires the argument to be quoted e.g. --time "1234.567,1234.789 1235," | |
a91f4c47 | 409 | |
0ccc69ba | 410 | Also support time percent with multiple time ranges. Time string is |
cc2ef584 | 411 | 'a%/n,b%/m,...' or 'a%-b%,c%-%d,...'. |
2ab046cd JY |
412 | |
413 | For example: | |
cc2ef584 | 414 | Select the second 10% time slice: |
2ab046cd JY |
415 | perf script --time 10%/2 |
416 | ||
cc2ef584 | 417 | Select from 0% to 10% time slice: |
2ab046cd JY |
418 | perf script --time 0%-10% |
419 | ||
cc2ef584 | 420 | Select the first and second 10% time slices: |
2ab046cd JY |
421 | perf script --time 10%/1,10%/2 |
422 | ||
cc2ef584 | 423 | Select from 0% to 10% and 30% to 40% slices: |
2ab046cd JY |
424 | perf script --time 0%-10%,30%-40% |
425 | ||
48d02a1d | 426 | --max-blocks:: |
5f8eec32 | 427 | Set the maximum number of program blocks to print with brstackinsn for |
48d02a1d AK |
428 | each sample. |
429 | ||
90b10f47 AK |
430 | --reltime:: |
431 | Print time stamps relative to trace start. | |
432 | ||
26567ed7 HPP |
433 | --deltatime:: |
434 | Print time stamps relative to previous event. | |
435 | ||
a14390fd ACM |
436 | --per-event-dump:: |
437 | Create per event files with a "perf.data.EVENT.dump" name instead of | |
438 | printing to stdout, useful, for instance, for generating flamegraphs. | |
439 | ||
325fbff5 NK |
440 | --inline:: |
441 | If a callgraph address belongs to an inlined function, the inline stack | |
d8a88dd2 MW |
442 | will be printed. Each entry has function name and file/line. Enabled by |
443 | default, disable with --no-inline. | |
325fbff5 | 444 | |
6750ba4b CD |
445 | --insn-trace[=<raw|disasm>]:: |
446 | Show instruction stream in bytes (raw) or disassembled (disasm) | |
447 | for intel_pt traces. The default is 'raw'. To use xed, combine | |
448 | 'raw' with --xed to show disassembly done by xed. | |
b585ebdb AK |
449 | |
450 | --xed:: | |
451 | Run xed disassembler on output. Requires installing the xed disassembler. | |
452 | ||
628d736d IR |
453 | -S:: |
454 | --symbols=symbol[,symbol...]:: | |
455 | Only consider the listed symbols. Symbols are typically a name | |
456 | but they may also be hexadecimal address. | |
457 | ||
61d9fc44 JY |
458 | The hexadecimal address may be the start address of a symbol or |
459 | any other address to filter the trace records | |
460 | ||
628d736d IR |
461 | For example, to select the symbol noploop or the address 0x4007a0: |
462 | perf script --symbols=noploop,0x4007a0 | |
463 | ||
61d9fc44 JY |
464 | Support filtering trace records by symbol name, start address of |
465 | symbol, any hexadecimal address and address range. | |
466 | ||
467 | The comparison order is: | |
468 | ||
469 | 1. symbol name comparison | |
470 | 2. symbol start address comparison. | |
471 | 3. any hexadecimal address comparison. | |
472 | 4. address range comparison (see --addr-range). | |
473 | ||
474 | --addr-range:: | |
475 | Use with -S or --symbols to list traced records within address range. | |
476 | ||
477 | For example, to list the traced records within the address range | |
478 | [0x4007a0, 0x0x4007a9]: | |
479 | perf script -S 0x4007a0 --addr-range 10 | |
480 | ||
4b799a9b JY |
481 | --dsos=:: |
482 | Only consider symbols in these DSOs. | |
483 | ||
d1b1552e AK |
484 | --call-trace:: |
485 | Show call stream for intel_pt traces. The CPUs are interleaved, but | |
486 | can be filtered with -C. | |
487 | ||
488 | --call-ret-trace:: | |
489 | Show call and return stream for intel_pt traces. | |
490 | ||
99f753f0 AK |
491 | --graph-function:: |
492 | For itrace only show specified functions and their callees for | |
493 | itrace. Multiple functions can be separated by comma. | |
494 | ||
f90a2417 ACM |
495 | --switch-on EVENT_NAME:: |
496 | Only consider events after this event is found. | |
497 | ||
dd41f660 ACM |
498 | --switch-off EVENT_NAME:: |
499 | Stop considering events after this event is found. | |
500 | ||
6469eb6d | 501 | --show-on-off-events:: |
dd41f660 | 502 | Show the --switch-on/off events too. |
6469eb6d | 503 | |
680d125c KL |
504 | --stitch-lbr:: |
505 | Show callgraph with stitched LBRs, which may have more complete | |
506 | callgraph. The perf.data file must have been obtained using | |
507 | perf record --call-graph lbr. | |
508 | Disabled by default. In common cases with call stack overflows, | |
509 | it can recreate better call stacks than the default lbr call stack | |
4cbd5334 | 510 | output. But this approach is not foolproof. There can be cases |
680d125c KL |
511 | where it creates incorrect call stacks from incorrect matches. |
512 | The known limitations include exception handing such as | |
513 | setjmp/longjmp will have calls/returns not match. | |
514 | ||
53e76d35 AH |
515 | :GMEXAMPLECMD: script |
516 | :GMEXAMPLESUBCMD: | |
517 | include::guest-files.txt[] | |
5b208144 | 518 | |
0a02ad93 IM |
519 | SEE ALSO |
520 | -------- | |
133dc4c3 | 521 | linkperf:perf-record[1], linkperf:perf-script-perl[1], |
291961fc AH |
522 | linkperf:perf-script-python[1], linkperf:perf-intel-pt[1], |
523 | linkperf:perf-dlfilter[1] |