perf-record - Run a command and record its profile into perf.data
perf record [-e <EVENT> | --event=EVENT] [-l] [-a] <command>
perf record [-e <EVENT> | --event=EVENT] [-l] [-a] — <command> [<options>]
This command runs a command and gathers a performance counter profile
from it, into perf.data - without displaying anything.
This file can then be inspected later on, using perf report.
Any command you can specify in a shell.
Select the PMU event. Selection can be:
· a symbolic event name (use perf list to list all events)
· a raw PMU event (eventsel+umask) in the form of rNNN where NNN
is a hexadecimal event descriptor.
· a hardware breakpoint event in the form of \mem:addr[:access]
where addr is the address in memory you want to break in.
Access is the memory access type (read, write, execute) it can
be passed as follows: \mem:addr[:[r][w][x]]. If you want to
profile read-write accesses in 0x1000, just set mem:0x1000:rw.
System-wide collection from all CPUs.
Scale counter values.
Record events on existing process ID.
Record events on existing thread ID.
Collect data with this RT SCHED_FIFO priority.
Collect data without buffering.
Append to the output file to do incremental profiling.
Overwrite existing data file. (deprecated)
Event period to sample.
Output file name.
Child tasks do not inherit counters.
Profile at this frequency.
Number of mmap data pages.
Do call-graph (stack chain/backtrace) recording.
Don’t print any message, useful for scripting.
Be more verbose (show counter open errors, etc).
Per thread counts.
Sample timestamps. Use it with perf report -D to see the
timestamps, for instance.
Collect raw sample records from all opened counters (default for
Collect samples only on the list of CPUs provided. Multiple CPUs
can be provided as a comma-separated list with no space: 0,1.
Ranges of CPUs are specified with -: 0-2. In per-thread mode with
inheritance mode on (default), samples are captured only when the
thread executes on the designated CPUs. Default is to monitor all
Do not update the builid cache. This saves some overhead in
situations where the information in the perf.data file (which
includes buildids) is sufficient.