1perf-report(1)
2==============
3
4NAME
5----
6perf-report - Read perf.data (created by perf record) and display the profile
7
8SYNOPSIS
9--------
10[verse]
11'perf report' [-i <file> | --input=file]
12
13DESCRIPTION
14-----------
15This command displays the performance counter profile information recorded
16via perf record.
17
18OPTIONS
19-------
20-i::
21--input=::
22        Input file name. (default: perf.data unless stdin is a fifo)
23
24-v::
25--verbose::
26        Be more verbose. (show symbol address, etc)
27
28-q::
29--quiet::
30	Do not show any message.  (Suppress -v)
31
32-n::
33--show-nr-samples::
34	Show the number of samples for each symbol
35
36--show-cpu-utilization::
37        Show sample percentage for different cpu modes.
38
39-T::
40--threads::
41	Show per-thread event counters.  The input data file should be recorded
42	with -s option.
43-c::
44--comms=::
45	Only consider symbols in these comms. CSV that understands
46	file://filename entries.  This option will affect the percentage of
47	the overhead column.  See --percentage for more info.
48--pid=::
49        Only show events for given process ID (comma separated list).
50
51--tid=::
52        Only show events for given thread ID (comma separated list).
53-d::
54--dsos=::
55	Only consider symbols in these dsos. CSV that understands
56	file://filename entries.  This option will affect the percentage of
57	the overhead column.  See --percentage for more info.
58-S::
59--symbols=::
60	Only consider these symbols. CSV that understands
61	file://filename entries.  This option will affect the percentage of
62	the overhead column.  See --percentage for more info.
63
64--symbol-filter=::
65	Only show symbols that match (partially) with this filter.
66
67-U::
68--hide-unresolved::
69        Only display entries resolved to a symbol.
70
71-s::
72--sort=::
73	Sort histogram entries by given key(s) - multiple keys can be specified
74	in CSV format.  Following sort keys are available:
75	pid, comm, dso, symbol, parent, cpu, socket, srcline, weight,
76	local_weight, cgroup_id.
77
78	Each key has following meaning:
79
80	- comm: command (name) of the task which can be read via /proc/<pid>/comm
81	- pid: command and tid of the task
82	- dso: name of library or module executed at the time of sample
83	- dso_size: size of library or module executed at the time of sample
84	- symbol: name of function executed at the time of sample
85	- symbol_size: size of function executed at the time of sample
86	- parent: name of function matched to the parent regex filter. Unmatched
87	entries are displayed as "[other]".
88	- cpu: cpu number the task ran at the time of sample
89	- socket: processor socket number the task ran at the time of sample
90	- srcline: filename and line number executed at the time of sample.  The
91	DWARF debugging info must be provided.
92	- srcfile: file name of the source file of the samples. Requires dwarf
93	information.
94	- weight: Event specific weight, e.g. memory latency or transaction
95	abort cost. This is the global weight.
96	- local_weight: Local weight version of the weight above.
97	- cgroup_id: ID derived from cgroup namespace device and inode numbers.
98	- cgroup: cgroup pathname in the cgroupfs.
99	- transaction: Transaction abort flags.
100	- overhead: Overhead percentage of sample
101	- overhead_sys: Overhead percentage of sample running in system mode
102	- overhead_us: Overhead percentage of sample running in user mode
103	- overhead_guest_sys: Overhead percentage of sample running in system mode
104	on guest machine
105	- overhead_guest_us: Overhead percentage of sample running in user mode on
106	guest machine
107	- sample: Number of sample
108	- period: Raw number of event count of sample
109	- time: Separate the samples by time stamp with the resolution specified by
110	--time-quantum (default 100ms). Specify with overhead and before it.
111
112	By default, comm, dso and symbol keys are used.
113	(i.e. --sort comm,dso,symbol)
114
115	If --branch-stack option is used, following sort keys are also
116	available:
117
118	- dso_from: name of library or module branched from
119	- dso_to: name of library or module branched to
120	- symbol_from: name of function branched from
121	- symbol_to: name of function branched to
122	- srcline_from: source file and line branched from
123	- srcline_to: source file and line branched to
124	- mispredict: "N" for predicted branch, "Y" for mispredicted branch
125	- in_tx: branch in TSX transaction
126	- abort: TSX transaction abort.
127	- cycles: Cycles in basic block
128
129	And default sort keys are changed to comm, dso_from, symbol_from, dso_to
130	and symbol_to, see '--branch-stack'.
131
132	When the sort key symbol is specified, columns "IPC" and "IPC Coverage"
133	are enabled automatically. Column "IPC" reports the average IPC per function
134	and column "IPC coverage" reports the percentage of instructions with
135	sampled IPC in this function. IPC means Instruction Per Cycle. If it's low,
136	it indicates there may be a performance bottleneck when the function is
137	executed, such as a memory access bottleneck. If a function has high overhead
138	and low IPC, it's worth further analyzing it to optimize its performance.
139
140	If the --mem-mode option is used, the following sort keys are also available
141	(incompatible with --branch-stack):
142	symbol_daddr, dso_daddr, locked, tlb, mem, snoop, dcacheline.
143
144	- symbol_daddr: name of data symbol being executed on at the time of sample
145	- dso_daddr: name of library or module containing the data being executed
146	on at the time of the sample
147	- locked: whether the bus was locked at the time of the sample
148	- tlb: type of tlb access for the data at the time of the sample
149	- mem: type of memory access for the data at the time of the sample
150	- snoop: type of snoop (if any) for the data at the time of the sample
151	- dcacheline: the cacheline the data address is on at the time of the sample
152	- phys_daddr: physical address of data being executed on at the time of sample
153	- data_page_size: the data page size of data being executed on at the time of sample
154
155	And the default sort keys are changed to local_weight, mem, sym, dso,
156	symbol_daddr, dso_daddr, snoop, tlb, locked, see '--mem-mode'.
157
158	If the data file has tracepoint event(s), following (dynamic) sort keys
159	are also available:
160	trace, trace_fields, [<event>.]<field>[/raw]
161
162	- trace: pretty printed trace output in a single column
163	- trace_fields: fields in tracepoints in separate columns
164	- <field name>: optional event and field name for a specific field
165
166	The last form consists of event and field names.  If event name is
167	omitted, it searches all events for matching field name.  The matched
168	field will be shown only for the event has the field.  The event name
169	supports substring match so user doesn't need to specify full subsystem
170	and event name everytime.  For example, 'sched:sched_switch' event can
171	be shortened to 'switch' as long as it's not ambiguous.  Also event can
172	be specified by its index (starting from 1) preceded by the '%'.
173	So '%1' is the first event, '%2' is the second, and so on.
174
175	The field name can have '/raw' suffix which disables pretty printing
176	and shows raw field value like hex numbers.  The --raw-trace option
177	has the same effect for all dynamic sort keys.
178
179	The default sort keys are changed to 'trace' if all events in the data
180	file are tracepoint.
181
182-F::
183--fields=::
184	Specify output field - multiple keys can be specified in CSV format.
185	Following fields are available:
186	overhead, overhead_sys, overhead_us, overhead_children, sample and period.
187	Also it can contain any sort key(s).
188
189	By default, every sort keys not specified in -F will be appended
190	automatically.
191
192	If the keys starts with a prefix '+', then it will append the specified
193        field(s) to the default field order. For example: perf report -F +period,sample.
194
195-p::
196--parent=<regex>::
197        A regex filter to identify parent. The parent is a caller of this
198	function and searched through the callchain, thus it requires callchain
199	information recorded. The pattern is in the extended regex format and
200	defaults to "\^sys_|^do_page_fault", see '--sort parent'.
201
202-x::
203--exclude-other::
204        Only display entries with parent-match.
205
206-w::
207--column-widths=<width[,width...]>::
208	Force each column width to the provided list, for large terminal
209	readability.  0 means no limit (default behavior).
210
211-t::
212--field-separator=::
213	Use a special separator character and don't pad with spaces, replacing
214	all occurrences of this separator in symbol names (and other output)
215	with a '.' character, that thus it's the only non valid separator.
216
217-D::
218--dump-raw-trace::
219        Dump raw trace in ASCII.
220
221-g::
222--call-graph=<print_type,threshold[,print_limit],order,sort_key[,branch],value>::
223        Display call chains using type, min percent threshold, print limit,
224	call order, sort key, optional branch and value.  Note that ordering
225	is not fixed so any parameter can be given in an arbitrary order.
226	One exception is the print_limit which should be preceded by threshold.
227
228	print_type can be either:
229	- flat: single column, linear exposure of call chains.
230	- graph: use a graph tree, displaying absolute overhead rates. (default)
231	- fractal: like graph, but displays relative rates. Each branch of
232		 the tree is considered as a new profiled object.
233	- folded: call chains are displayed in a line, separated by semicolons
234	- none: disable call chain display.
235
236	threshold is a percentage value which specifies a minimum percent to be
237	included in the output call graph.  Default is 0.5 (%).
238
239	print_limit is only applied when stdio interface is used.  It's to limit
240	number of call graph entries in a single hist entry.  Note that it needs
241	to be given after threshold (but not necessarily consecutive).
242	Default is 0 (unlimited).
243
244	order can be either:
245	- callee: callee based call graph.
246	- caller: inverted caller based call graph.
247	Default is 'caller' when --children is used, otherwise 'callee'.
248
249	sort_key can be:
250	- function: compare on functions (default)
251	- address: compare on individual code addresses
252	- srcline: compare on source filename and line number
253
254	branch can be:
255	- branch: include last branch information in callgraph when available.
256	          Usually more convenient to use --branch-history for this.
257
258	value can be:
259	- percent: display overhead percent (default)
260	- period: display event period
261	- count: display event count
262
263--children::
264	Accumulate callchain of children to parent entry so that then can
265	show up in the output.  The output will have a new "Children" column
266	and will be sorted on the data.  It requires callchains are recorded.
267	See the `overhead calculation' section for more details. Enabled by
268	default, disable with --no-children.
269
270--max-stack::
271	Set the stack depth limit when parsing the callchain, anything
272	beyond the specified depth will be ignored. This is a trade-off
273	between information loss and faster processing especially for
274	workloads that can have a very long callchain stack.
275	Note that when using the --itrace option the synthesized callchain size
276	will override this value if the synthesized callchain size is bigger.
277
278	Default: 127
279
280-G::
281--inverted::
282        alias for inverted caller based call graph.
283
284--ignore-callees=<regex>::
285        Ignore callees of the function(s) matching the given regex.
286        This has the effect of collecting the callers of each such
287        function into one place in the call-graph tree.
288
289--pretty=<key>::
290        Pretty printing style.  key: normal, raw
291
292--stdio:: Use the stdio interface.
293
294--stdio-color::
295	'always', 'never' or 'auto', allowing configuring color output
296	via the command line, in addition to via "color.ui" .perfconfig.
297	Use '--stdio-color always' to generate color even when redirecting
298	to a pipe or file. Using just '--stdio-color' is equivalent to
299	using 'always'.
300
301--tui:: Use the TUI interface, that is integrated with annotate and allows
302        zooming into DSOs or threads, among other features. Use of --tui
303	requires a tty, if one is not present, as when piping to other
304	commands, the stdio interface is used.
305
306--gtk:: Use the GTK2 interface.
307
308-k::
309--vmlinux=<file>::
310        vmlinux pathname
311
312--ignore-vmlinux::
313	Ignore vmlinux files.
314
315--kallsyms=<file>::
316        kallsyms pathname
317
318-m::
319--modules::
320        Load module symbols. WARNING: This should only be used with -k and
321        a LIVE kernel.
322
323-f::
324--force::
325        Don't do ownership validation.
326
327--symfs=<directory>::
328        Look for files with symbols relative to this directory.
329
330-C::
331--cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can
332	be provided as a comma-separated list with no space: 0,1. Ranges of
333	CPUs are specified with -: 0-2. Default is to report samples on all
334	CPUs.
335
336-M::
337--disassembler-style=:: Set disassembler style for objdump.
338
339--source::
340	Interleave source code with assembly code. Enabled by default,
341	disable with --no-source.
342
343--asm-raw::
344	Show raw instruction encoding of assembly instructions.
345
346--show-total-period:: Show a column with the sum of periods.
347
348-I::
349--show-info::
350	Display extended information about the perf.data file. This adds
351	information which may be very large and thus may clutter the display.
352	It currently includes: cpu and numa topology of the host system.
353
354-b::
355--branch-stack::
356	Use the addresses of sampled taken branches instead of the instruction
357	address to build the histograms. To generate meaningful output, the
358	perf.data file must have been obtained using perf record -b or
359	perf record --branch-filter xxx where xxx is a branch filter option.
360	perf report is able to auto-detect whether a perf.data file contains
361	branch stacks and it will automatically switch to the branch view mode,
362	unless --no-branch-stack is used.
363
364--branch-history::
365	Add the addresses of sampled taken branches to the callstack.
366	This allows to examine the path the program took to each sample.
367	The data collection must have used -b (or -j) and -g.
368
369--objdump=<path>::
370        Path to objdump binary.
371
372--prefix=PREFIX::
373--prefix-strip=N::
374	Remove first N entries from source file path names in executables
375	and add PREFIX. This allows to display source code compiled on systems
376	with different file system layout.
377
378--group::
379	Show event group information together. It forces group output also
380	if there are no groups defined in data file.
381
382--group-sort-idx::
383	Sort the output by the event at the index n in group. If n is invalid,
384	sort by the first event. It can support multiple groups with different
385	amount of events. WARNING: This should be used on grouped events.
386
387--demangle::
388	Demangle symbol names to human readable form. It's enabled by default,
389	disable with --no-demangle.
390
391--demangle-kernel::
392	Demangle kernel symbol names to human readable form (for C++ kernels).
393
394--mem-mode::
395	Use the data addresses of samples in addition to instruction addresses
396	to build the histograms.  To generate meaningful output, the perf.data
397	file must have been obtained using perf record -d -W and using a
398	special event -e cpu/mem-loads/p or -e cpu/mem-stores/p. See
399	'perf mem' for simpler access.
400
401--percent-limit::
402	Do not show entries which have an overhead under that percent.
403	(Default: 0).  Note that this option also sets the percent limit (threshold)
404	of callchains.  However the default value of callchain threshold is
405	different than the default value of hist entries.  Please see the
406	--call-graph option for details.
407
408--percentage::
409	Determine how to display the overhead percentage of filtered entries.
410	Filters can be applied by --comms, --dsos and/or --symbols options and
411	Zoom operations on the TUI (thread, dso, etc).
412
413	"relative" means it's relative to filtered entries only so that the
414	sum of shown entries will be always 100%.  "absolute" means it retains
415	the original value before and after the filter is applied.
416
417--header::
418	Show header information in the perf.data file.  This includes
419	various information like hostname, OS and perf version, cpu/mem
420	info, perf command line, event list and so on.  Currently only
421	--stdio output supports this feature.
422
423--header-only::
424	Show only perf.data header (forces --stdio).
425
426--time::
427	Only analyze samples within given time window: <start>,<stop>. Times
428	have the format seconds.nanoseconds. If start is not given (i.e. time
429	string is ',x.y') then analysis starts at the beginning of the file. If
430	stop time is not given (i.e. time string is 'x.y,') then analysis goes
431	to end of file. Multiple ranges can be separated by spaces, which
432	requires the argument to be quoted e.g. --time "1234.567,1234.789 1235,"
433
434	Also support time percent with multiple time ranges. Time string is
435	'a%/n,b%/m,...' or 'a%-b%,c%-%d,...'.
436
437	For example:
438	Select the second 10% time slice:
439
440	  perf report --time 10%/2
441
442	Select from 0% to 10% time slice:
443
444	  perf report --time 0%-10%
445
446	Select the first and second 10% time slices:
447
448	  perf report --time 10%/1,10%/2
449
450	Select from 0% to 10% and 30% to 40% slices:
451
452	  perf report --time 0%-10%,30%-40%
453
454--switch-on EVENT_NAME::
455	Only consider events after this event is found.
456
457	This may be interesting to measure a workload only after some initialization
458	phase is over, i.e. insert a perf probe at that point and then using this
459	option with that probe.
460
461--switch-off EVENT_NAME::
462	Stop considering events after this event is found.
463
464--show-on-off-events::
465	Show the --switch-on/off events too. This has no effect in 'perf report' now
466	but probably we'll make the default not to show the switch-on/off events
467        on the --group mode and if there is only one event besides the off/on ones,
468	go straight to the histogram browser, just like 'perf report' with no events
469	explicitely specified does.
470
471--itrace::
472	Options for decoding instruction tracing data. The options are:
473
474include::itrace.txt[]
475
476	To disable decoding entirely, use --no-itrace.
477
478--full-source-path::
479	Show the full path for source files for srcline output.
480
481--show-ref-call-graph::
482	When multiple events are sampled, it may not be needed to collect
483	callgraphs for all of them. The sample sites are usually nearby,
484	and it's enough to collect the callgraphs on a reference event.
485	So user can use "call-graph=no" event modifier to disable callgraph
486	for other events to reduce the overhead.
487	However, perf report cannot show callgraphs for the event which
488	disable the callgraph.
489	This option extends the perf report to show reference callgraphs,
490	which collected by reference event, in no callgraph event.
491
492--stitch-lbr::
493	Show callgraph with stitched LBRs, which may have more complete
494	callgraph. The perf.data file must have been obtained using
495	perf record --call-graph lbr.
496	Disabled by default. In common cases with call stack overflows,
497	it can recreate better call stacks than the default lbr call stack
498	output. But this approach is not full proof. There can be cases
499	where it creates incorrect call stacks from incorrect matches.
500	The known limitations include exception handing such as
501	setjmp/longjmp will have calls/returns not match.
502
503--socket-filter::
504	Only report the samples on the processor socket that match with this filter
505
506--samples=N::
507	Save N individual samples for each histogram entry to show context in perf
508	report tui browser.
509
510--raw-trace::
511	When displaying traceevent output, do not use print fmt or plugins.
512
513--hierarchy::
514	Enable hierarchical output.
515
516--inline::
517	If a callgraph address belongs to an inlined function, the inline stack
518	will be printed. Each entry is function name or file/line. Enabled by
519	default, disable with --no-inline.
520
521--mmaps::
522	Show --tasks output plus mmap information in a format similar to
523	/proc/<PID>/maps.
524
525	Please note that not all mmaps are stored, options affecting which ones
526	are include 'perf record --data', for instance.
527
528--ns::
529	Show time stamps in nanoseconds.
530
531--stats::
532	Display overall events statistics without any further processing.
533	(like the one at the end of the perf report -D command)
534
535--tasks::
536	Display monitored tasks stored in perf data. Displaying pid/tid/ppid
537	plus the command string aligned to distinguish parent and child tasks.
538
539--percent-type::
540	Set annotation percent type from following choices:
541	  global-period, local-period, global-hits, local-hits
542
543	The local/global keywords set if the percentage is computed
544	in the scope of the function (local) or the whole data (global).
545	The period/hits keywords set the base the percentage is computed
546	on - the samples period or the number of samples (hits).
547
548--time-quantum::
549	Configure time quantum for time sort key. Default 100ms.
550	Accepts s, us, ms, ns units.
551
552--total-cycles::
553	When --total-cycles is specified, it supports sorting for all blocks by
554	'Sampled Cycles%'. This is useful to concentrate on the globally hottest
555	blocks. In output, there are some new columns:
556
557	'Sampled Cycles%' - block sampled cycles aggregation / total sampled cycles
558	'Sampled Cycles'  - block sampled cycles aggregation
559	'Avg Cycles%'     - block average sampled cycles / sum of total block average
560			    sampled cycles
561	'Avg Cycles'      - block average sampled cycles
562
563include::callchain-overhead-calculation.txt[]
564
565SEE ALSO
566--------
567linkperf:perf-stat[1], linkperf:perf-annotate[1], linkperf:perf-record[1],
568linkperf:perf-intel-pt[1]
569