1perf-record(1)
2==============
3
4NAME
5----
6perf-record - Run a command and record its profile into perf.data
7
8SYNOPSIS
9--------
10[verse]
11'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] <command>
12'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] -- <command> [<options>]
13
14DESCRIPTION
15-----------
16This command runs a command and gathers a performance counter profile
17from it, into perf.data - without displaying anything.
18
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=::
29	Select the PMU event. Selection can be:
30
31        - 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
36	- 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
48	  There are also some params which are not defined in .../<pmu>/format/*.
49	  These params can be used to overload default config values per event.
50	  Here is a list of the params.
51	  - 'period': Set event sampling period
52	  - 'freq': Set event sampling frequency
53	  - 'time': Disable/enable time stamping. Acceptable values are 1 for
54		    enabling time stamping. 0 for disabling time stamping.
55		    The default is 1.
56	  - 'call-graph': Disable/enable callgraph. Acceptable str are "fp" for
57			 FP mode, "dwarf" for DWARF mode, "lbr" for LBR mode and
58			 "no" for disable callgraph.
59	  - 'stack-size': user stack size for dwarf mode
60	  Note: If user explicitly sets options which conflict with the params,
61	  the value set by the params will be overridden.
62
63        - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
64          where addr is the address in memory you want to break in.
65          Access is the memory access type (read, write, execute) it can
66          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.
68          If you want to profile read-write accesses in 0x1000, just set
69          'mem:0x1000:rw'.
70          If you want to profile write accesses in [0x1000~1008), just set
71          'mem:0x1000/8:w'.
72
73	- 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
78--filter=<filter>::
79        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 '&&'.
89
90-a::
91--all-cpus::
92        System-wide collection from all CPUs.
93
94-p::
95--pid=::
96	Record events on existing process ID (comma separated list).
97
98-t::
99--tid=::
100        Record events on existing thread ID (comma separated list).
101        This option also disables inheritance by default.  Enable it by adding
102        --inherit.
103
104-u::
105--uid=::
106        Record events in threads owned by uid. Name or number.
107
108-r::
109--realtime=::
110	Collect data with this RT SCHED_FIFO priority.
111
112--no-buffering::
113	Collect data without buffering.
114
115-c::
116--count=::
117	Event period to sample.
118
119-o::
120--output=::
121	Output file name.
122
123-i::
124--no-inherit::
125	Child tasks do not inherit counters.
126-F::
127--freq=::
128	Profile at this frequency.
129
130-m::
131--mmap-pages=::
132	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.
135	Also, by adding a comma, the number of mmap pages for AUX
136	area tracing can be specified.
137
138--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
142-g::
143	Enables call-graph (stack chain/backtrace) recording.
144
145--call-graph::
146	Setup and enable call-graph (stack chain/backtrace) recording,
147	implies -g.
148
149	Allows specifying "fp" (frame pointer) or "dwarf"
150	(DWARF's CFI - Call Frame Information) or "lbr"
151	(Hardware Last Branch Record facility) as the method to collect
152	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.
158	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.
163
164-q::
165--quiet::
166	Don't print any message, useful for scripting.
167
168-v::
169--verbose::
170	Be more verbose (show counter open errors, etc).
171
172-s::
173--stat::
174	Record per-thread event counts.  Use it with 'perf report -T' to see
175	the values.
176
177-d::
178--data::
179	Record the sample addresses.
180
181-T::
182--timestamp::
183	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.
189
190-n::
191--no-samples::
192	Don't sample.
193
194-R::
195--raw-samples::
196Collect raw sample records from all opened counters (default for tracepoint counters).
197
198-C::
199--cpu::
200Collect 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.
202In 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
205-N::
206--no-buildid-cache::
207Do not update the buildid cache. This saves some overhead in situations
208where the information in the perf.data file (which includes buildids)
209is sufficient.
210
211-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
222-b::
223--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::
229Enable 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
235        - any:  any type of branches
236        - any_call: any function call or system call
237        - any_ret: any function return or system call return
238        - ind_call: any indirect branch
239        - 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
242	- 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
245	- cond: conditional branches
246
247+
248The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
249The privilege levels may be omitted, in which case, the privilege levels of the associated
250event 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.
255
256--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
261--transaction::
262Record transaction flags for transaction related events.
263
264--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.
269
270-D::
271--delay=::
272After 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
275-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. It is possible to select the registers to sample using their
280symbolic names, e.g. on x86, ax, si. To list the available registers use
281--intr-regs=\?. To name registers, pass a comma separated list such as
282--intr-regs=ax,bx. The list of register is architecture dependent.
283
284
285--running-time::
286Record running and enabled time for read events (:S)
287
288-k::
289--clockid::
290Sets the clock id to use for the various time fields in the perf_event_type
291records. See clock_gettime(). In particular CLOCK_MONOTONIC and
292CLOCK_MONOTONIC_RAW are supported, some events might also allow
293CLOCK_BOOTTIME, CLOCK_REALTIME and CLOCK_TAI.
294
295-S::
296--snapshot::
297Select AUX area tracing Snapshot Mode. This option is valid only with an
298AUX area tracing event. Optionally the number of bytes to capture per
299snapshot can be specified. In Snapshot Mode, trace data is captured only when
300signal SIGUSR2 is received.
301
302--proc-map-timeout::
303When processing pre-existing threads /proc/XXX/mmap, it may take a long time,
304because the file may be huge. A time out is needed in such cases.
305This option sets the time out limit. The default value is 500 ms.
306
307--switch-events::
308Record context switch events i.e. events of type PERF_RECORD_SWITCH or
309PERF_RECORD_SWITCH_CPU_WIDE.
310
311SEE ALSO
312--------
313linkperf:perf-stat[1], linkperf:perf-list[1]
314