blob: 0ff23de9e4539599acdba5a8ade8325117e75caa [file] [log] [blame]
perf-record - Run a command and record its profile into
'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 - 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) or a raw PMU
event (eventsel+umask) in the form of rNNN where NNN is a
hexadecimal event descriptor.
System-wide collection.
Scale counter values.
Record events on existing pid.
Collect data with this RT SCHED_FIFO priority.
Append to the output file to do incremental profiling.
Overwrite existing data file.
Event period to sample.
Output file name.
Child tasks inherit counters.
Profile at this frequency.
Number of mmap data pages.
Do call-graph (stack chain/backtrace) recording.
Be more verbose (show counter open errors, etc).
Per thread counts.
Sample addresses.
Don't sample.
Collect raw sample records from all opened counters (typically for tracepoint counters).
linkperf:perf-stat[1], linkperf:perf-list[1]