blob: 347a27322ed81388faa4e5c8cfe8e95e741e34b7 [file] [log] [blame]
Ingo Molnare33e0a42009-04-20 15:58:01 +02001perf-record(1)
Ingo Molnarc1c23652009-05-30 12:38:51 +02002==============
Ingo Molnare33e0a42009-04-20 15:58:01 +02003
4NAME
5----
Ingo Molnar23ac9cb2009-05-27 09:33:18 +02006perf-record - Run a command and record its profile into perf.data
Ingo Molnare33e0a42009-04-20 15:58:01 +02007
8SYNOPSIS
9--------
10[verse]
11'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] <command>
Mike Galbraith9e0967532009-05-28 16:25:34 +020012'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] -- <command> [<options>]
Ingo Molnare33e0a42009-04-20 15:58:01 +020013
14DESCRIPTION
15-----------
16This command runs a command and gathers a performance counter profile
Ingo Molnar23ac9cb2009-05-27 09:33:18 +020017from it, into perf.data - without displaying anything.
Ingo Molnare33e0a42009-04-20 15:58:01 +020018
19This file can then be inspected later on, using 'perf report'.
20
21
22OPTIONS
23-------
24<command>...::
25 Any command you can specify in a shell.
26
27-e::
28--event=::
Frederic Weisbecker1b290d62009-11-23 15:42:35 +010029 Select the PMU event. Selection can be:
Ingo Molnare33e0a42009-04-20 15:58:01 +020030
Frederic Weisbecker1b290d62009-11-23 15:42:35 +010031 - a symbolic event name (use 'perf list' to list all events)
32
33 - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
34 hexadecimal event descriptor.
35
Cody P Schaferf9ab9c12015-01-07 17:13:53 -080036 - a symbolically formed PMU event like 'pmu/param1=0x3,param2/' where
37 'param1', 'param2', etc are defined as formats for the PMU in
38 /sys/bus/event_sources/devices/<pmu>/format/*.
39
40 - a symbolically formed event like 'pmu/config=M,config1=N,config3=K/'
41
42 where M, N, K are numbers (in decimal, hex, octal format). Acceptable
43 values for each of 'config', 'config1' and 'config2' are defined by
44 corresponding entries in /sys/bus/event_sources/devices/<pmu>/format/*
45 param1 and param2 are defined as formats for the PMU in:
46 /sys/bus/event_sources/devices/<pmu>/format/*
47
Kan Liang3d5d68a2015-07-08 04:44:54 -040048 There are also some params which are not defined in .../<pmu>/format/*.
Jiri Olsaee4c7582015-07-29 05:42:11 -040049 These params can be used to overload default config values per event.
Kan Liang3d5d68a2015-07-08 04:44:54 -040050 Here is a list of the params.
51 - 'period': Set event sampling period
Namhyung Kim09af2a52015-08-09 15:45:23 +090052 - 'freq': Set event sampling frequency
Kan Liang32067712015-08-04 04:30:19 -040053 - 'time': Disable/enable time stamping. Acceptable values are 1 for
54 enabling time stamping. 0 for disabling time stamping.
55 The default is 1.
Kan Liangd457c962015-08-11 06:30:47 -040056 - 'call-graph': Disable/enable callgraph. Acceptable str are "fp" for
Kan Liangf9db0d02015-08-11 06:30:48 -040057 FP mode, "dwarf" for DWARF mode, "lbr" for LBR mode and
58 "no" for disable callgraph.
Kan Liangd457c962015-08-11 06:30:47 -040059 - 'stack-size': user stack size for dwarf mode
Kan Liang3d5d68a2015-07-08 04:44:54 -040060 Note: If user explicitly sets options which conflict with the params,
61 the value set by the params will be overridden.
62
Jacob Shin3741eb92014-05-29 17:26:51 +020063 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
Frederic Weisbecker1b290d62009-11-23 15:42:35 +010064 where addr is the address in memory you want to break in.
65 Access is the memory access type (read, write, execute) it can
Jacob Shin3741eb92014-05-29 17:26:51 +020066 be passed as follows: '\mem:addr[:[r][w][x]]'. len is the range,
67 number of bytes from specified addr, which the breakpoint will cover.
Frederic Weisbecker1b290d62009-11-23 15:42:35 +010068 If you want to profile read-write accesses in 0x1000, just set
69 'mem:0x1000:rw'.
Jacob Shin3741eb92014-05-29 17:26:51 +020070 If you want to profile write accesses in [0x1000~1008), just set
71 'mem:0x1000/8:w'.
Shawn Bohrer08dbd7e2010-11-30 19:57:16 -060072
Namhyung Kim9a756062015-03-02 12:13:33 +090073 - a group of events surrounded by a pair of brace ("{event1,event2,...}").
74 Each event is separated by commas and the group should be quoted to
75 prevent the shell interpretation. You also need to use --group on
76 "perf report" to view group events together.
77
Shawn Bohrer08dbd7e2010-11-30 19:57:16 -060078--filter=<filter>::
Wang Nan4ba1faa2015-07-10 07:36:10 +000079 Event filter. This option should follow a event selector (-e) which
80 selects tracepoint event(s). Multiple '--filter' options are combined
81 using '&&'.
82
83--exclude-perf::
84 Don't record events issued by perf itself. This option should follow
85 a event selector (-e) which selects tracepoint event(s). It adds a
86 filter expression 'common_pid != $PERFPID' to filters. If other
87 '--filter' exists, the new filter expression will be combined with
88 them by '&&'.
Shawn Bohrer08dbd7e2010-11-30 19:57:16 -060089
Ingo Molnare33e0a42009-04-20 15:58:01 +020090-a::
Shawn Bohrer08dbd7e2010-11-30 19:57:16 -060091--all-cpus::
92 System-wide collection from all CPUs.
Ingo Molnare33e0a42009-04-20 15:58:01 +020093
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -030094-p::
95--pid=::
David Ahernb52956c2012-02-08 09:32:52 -070096 Record events on existing process ID (comma separated list).
Shawn Bohrer08dbd7e2010-11-30 19:57:16 -060097
98-t::
99--tid=::
David Ahernb52956c2012-02-08 09:32:52 -0700100 Record events on existing thread ID (comma separated list).
Adrian Hunter69e7e5b2013-11-18 11:55:57 +0200101 This option also disables inheritance by default. Enable it by adding
102 --inherit.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300103
Arnaldo Carvalho de Melo0d37aa32012-01-19 14:08:15 -0200104-u::
105--uid=::
106 Record events in threads owned by uid. Name or number.
107
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300108-r::
109--realtime=::
110 Collect data with this RT SCHED_FIFO priority.
Jiri Olsa563aecb2013-06-05 13:35:06 +0200111
Arnaldo Carvalho de Melo509051e2014-01-14 17:52:14 -0300112--no-buffering::
Kirill Smelkovacac03f2011-01-12 17:59:36 +0300113 Collect data without buffering.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300114
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300115-c::
116--count=::
117 Event period to sample.
118
119-o::
120--output=::
121 Output file name.
122
123-i::
Stephane Eranian2e6cdf92010-05-12 10:40:01 +0200124--no-inherit::
125 Child tasks do not inherit counters.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300126-F::
127--freq=::
128 Profile at this frequency.
129
130-m::
131--mmap-pages=::
Jiri Olsa27050f52013-09-01 12:36:13 +0200132 Number of mmap data pages (must be a power of two) or size
133 specification with appended unit character - B/K/M/G. The
134 size is rounded up to have nearest pages power of two value.
Adrian Huntere9db1312015-04-09 18:53:46 +0300135 Also, by adding a comma, the number of mmap pages for AUX
136 area tracing can be specified.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300137
Namhyung Kim9a756062015-03-02 12:13:33 +0900138--group::
139 Put all events in a single event group. This precedes the --event
140 option and remains only for backward compatibility. See --event.
141
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300142-g::
Jiri Olsa09b0fd42013-10-26 16:25:33 +0200143 Enables call-graph (stack chain/backtrace) recording.
144
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300145--call-graph::
Jiri Olsa09b0fd42013-10-26 16:25:33 +0200146 Setup and enable call-graph (stack chain/backtrace) recording,
147 implies -g.
148
149 Allows specifying "fp" (frame pointer) or "dwarf"
Kan Liangaad2b212015-01-05 13:23:04 -0500150 (DWARF's CFI - Call Frame Information) or "lbr"
151 (Hardware Last Branch Record facility) as the method to collect
Jiri Olsa09b0fd42013-10-26 16:25:33 +0200152 the information used to show the call graphs.
153
154 In some systems, where binaries are build with gcc
155 --fomit-frame-pointer, using the "fp" method will produce bogus
156 call graphs, using "dwarf", if available (perf tools linked to
157 the libunwind library) should be used instead.
Kan Liangaad2b212015-01-05 13:23:04 -0500158 Using the "lbr" method doesn't require any compiler options. It
159 will produce call graphs from the hardware LBR registers. The
160 main limition is that it is only available on new Intel
161 platforms, such as Haswell. It can only get user call chain. It
162 doesn't work with branch stack sampling at the same time.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300163
Arnaldo Carvalho de Melob44308f2010-10-26 15:20:09 -0200164-q::
165--quiet::
166 Don't print any message, useful for scripting.
167
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300168-v::
169--verbose::
170 Be more verbose (show counter open errors, etc).
171
172-s::
173--stat::
Namhyung Kim1f91d5f2015-05-10 00:19:42 +0900174 Record per-thread event counts. Use it with 'perf report -T' to see
175 the values.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300176
177-d::
178--data::
Peter Zijlstra56100322015-06-10 16:48:50 +0200179 Record the sample addresses.
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300180
Arnaldo Carvalho de Melo9c90a612010-12-02 10:25:28 -0200181-T::
182--timestamp::
Peter Zijlstra56100322015-06-10 16:48:50 +0200183 Record the sample timestamps. Use it with 'perf report -D' to see the
184 timestamps, for instance.
185
186-P::
187--period::
188 Record the sample period.
Arnaldo Carvalho de Melo9c90a612010-12-02 10:25:28 -0200189
Arnaldo Carvalho de Melo386c0b72009-08-05 10:04:53 -0300190-n::
191--no-samples::
192 Don't sample.
Ingo Molnare33e0a42009-04-20 15:58:01 +0200193
Frederic Weisbeckerec7ba4e2009-08-31 03:32:03 +0200194-R::
195--raw-samples::
Frederic Weisbeckerbdef3b02010-04-14 20:05:17 +0200196Collect raw sample records from all opened counters (default for tracepoint counters).
Frederic Weisbeckerec7ba4e2009-08-31 03:32:03 +0200197
Stephane Eranianc45c6ea2010-05-28 12:00:01 +0200198-C::
199--cpu::
Shawn Bohrer08dbd7e2010-11-30 19:57:16 -0600200Collect samples only on the list of CPUs provided. Multiple CPUs can be provided as a
201comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-2.
Stephane Eranianc45c6ea2010-05-28 12:00:01 +0200202In per-thread mode with inheritance mode on (default), samples are captured only when
203the thread executes on the designated CPUs. Default is to monitor all CPUs.
204
Stephane Eraniana1ac1d32010-06-17 11:39:01 +0200205-N::
206--no-buildid-cache::
Masanari Iida96355f22014-09-10 00:18:50 +0900207Do not update the buildid cache. This saves some overhead in situations
Stephane Eraniana1ac1d32010-06-17 11:39:01 +0200208where the information in the perf.data file (which includes buildids)
209is sufficient.
210
Stephane Eranian023695d2011-02-14 11:20:01 +0200211-G name,...::
212--cgroup name,...::
213monitor only in the container (cgroup) called "name". This option is available only
214in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
215container "name" are monitored when they run on the monitored CPUs. Multiple cgroups
216can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
217to first event, second cgroup to second event and so on. It is possible to provide
218an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
219corresponding events, i.e., they always refer to events defined earlier on the command
220line.
221
Roberto Agostino Vitillobdfebd82012-02-09 23:21:02 +0100222-b::
Stephane Eraniana5aabda2012-03-08 23:47:45 +0100223--branch-any::
224Enable taken branch stack sampling. Any type of taken branch may be sampled.
225This is a shortcut for --branch-filter any. See --branch-filter for more infos.
226
227-j::
228--branch-filter::
Roberto Agostino Vitillobdfebd82012-02-09 23:21:02 +0100229Enable taken branch stack sampling. Each sample captures a series of consecutive
230taken branches. The number of branches captured with each sample depends on the
231underlying hardware, the type of branches of interest, and the executed code.
232It is possible to select the types of branches captured by enabling filters. The
233following filters are defined:
234
Stephane Eraniana5aabda2012-03-08 23:47:45 +0100235 - any: any type of branches
Roberto Agostino Vitillobdfebd82012-02-09 23:21:02 +0100236 - any_call: any function call or system call
237 - any_ret: any function return or system call return
Anshuman Khandual2e49a942012-05-18 14:16:50 +0530238 - ind_call: any indirect branch
Roberto Agostino Vitillobdfebd82012-02-09 23:21:02 +0100239 - u: only when the branch target is at the user level
240 - k: only when the branch target is in the kernel
241 - hv: only when the target is at the hypervisor level
Andi Kleen0126d492013-09-20 07:40:42 -0700242 - in_tx: only when the target is in a hardware transaction
243 - no_tx: only when the target is not in a hardware transaction
244 - abort_tx: only when the target is a hardware transaction abort
Anshuman Khandual3e39db42014-05-22 12:50:10 +0530245 - cond: conditional branches
Roberto Agostino Vitillobdfebd82012-02-09 23:21:02 +0100246
247+
Anshuman Khandual3e39db42014-05-22 12:50:10 +0530248The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
Masanari Iida9c768202012-11-30 14:10:25 +0900249The privilege levels may be omitted, in which case, the privilege levels of the associated
Stephane Eraniana5aabda2012-03-08 23:47:45 +0100250event are applied to the branch filter. Both kernel (k) and hypervisor (hv) privilege
251levels are subject to permissions. When sampling on multiple events, branch stack sampling
252is enabled for all the sampling events. The sampled branch type is the same for all events.
253The various filters must be specified as a comma separated list: --branch-filter any_ret,u,k
254Note that this feature may not be available on all processors.
Roberto Agostino Vitillobdfebd82012-02-09 23:21:02 +0100255
Andi Kleen05484292013-01-24 16:10:29 +0100256--weight::
257Enable weightened sampling. An additional weight is recorded per sample and can be
258displayed with the weight and local_weight sort keys. This currently works for TSX
259abort events and some memory events in precise mode on modern Intel CPUs.
260
Andi Kleen475eeab2013-09-20 07:40:43 -0700261--transaction::
262Record transaction flags for transaction related events.
263
Adrian Hunter3aa59392013-11-15 15:52:29 +0200264--per-thread::
265Use per-thread mmaps. By default per-cpu mmaps are created. This option
266overrides that and uses per-thread mmaps. A side-effect of that is that
267inheritance is automatically disabled. --per-thread is ignored with a warning
268if combined with -a or -C options.
Adrian Hunter539e6bb2013-11-01 15:51:34 +0200269
Arnaldo Carvalho de Meloa6205a32014-01-14 17:58:12 -0300270-D::
271--delay=::
Andi Kleen6619a532014-01-11 13:38:27 -0800272After starting the program, wait msecs before measuring. This is useful to
273filter out the startup phase of the program, which is often very different.
274
Stephane Eranian4b6c5172014-09-24 13:48:41 +0200275-I::
276--intr-regs::
277Capture machine state (registers) at interrupt, i.e., on counter overflows for
278each sample. List of captured registers depends on the architecture. This option
279is off by default.
280
Andi Kleen85c273d2015-02-24 15:13:40 -0800281--running-time::
282Record running and enabled time for read events (:S)
283
Peter Zijlstra814c8c32015-03-31 00:19:31 +0200284-k::
285--clockid::
286Sets the clock id to use for the various time fields in the perf_event_type
287records. See clock_gettime(). In particular CLOCK_MONOTONIC and
288CLOCK_MONOTONIC_RAW are supported, some events might also allow
289CLOCK_BOOTTIME, CLOCK_REALTIME and CLOCK_TAI.
290
Adrian Hunter2dd6d8a2015-04-30 17:37:32 +0300291-S::
292--snapshot::
293Select AUX area tracing Snapshot Mode. This option is valid only with an
294AUX area tracing event. Optionally the number of bytes to capture per
295snapshot can be specified. In Snapshot Mode, trace data is captured only when
296signal SIGUSR2 is received.
297
Kan Liang9d9cad72015-06-17 09:51:11 -0400298--proc-map-timeout::
299When processing pre-existing threads /proc/XXX/mmap, it may take a long time,
300because the file may be huge. A time out is needed in such cases.
301This option sets the time out limit. The default value is 500 ms.
302
Adrian Hunterb757bb02015-07-21 12:44:04 +0300303--switch-events::
304Record context switch events i.e. events of type PERF_RECORD_SWITCH or
305PERF_RECORD_SWITCH_CPU_WIDE.
306
Ingo Molnare33e0a42009-04-20 15:58:01 +0200307SEE ALSO
308--------
Thomas Gleixner386b05e2009-06-06 14:56:33 +0200309linkperf:perf-stat[1], linkperf:perf-list[1]