6 perf-record - Run a command and record its profile into perf.data
11 'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] <command>
12 'perf record' [-e <EVENT> | --event=EVENT] [-l] [-a] -- <command> [<options>]
16 This command runs a command and gathers a performance counter profile
17 from it, into perf.data - without displaying anything.
19 This file can then be inspected later on, using 'perf report'.
25 Any command you can specify in a shell.
29 Select the PMU event. Selection can be:
31 - a symbolic event name (use 'perf list' to list all events)
33 - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
34 hexadecimal event descriptor.
36 - a hardware breakpoint event in the form of '\mem:addr[:access]'
37 where addr is the address in memory you want to break in.
38 Access is the memory access type (read, write, execute) it can
39 be passed as follows: '\mem:addr[:[r][w][x]]'.
40 If you want to profile read-write accesses in 0x1000, just set
43 System-wide collection.
50 Record events on existing pid.
54 Collect data with this RT SCHED_FIFO priority.
57 Append to the output file to do incremental profiling.
61 Overwrite existing data file.
65 Event period to sample.
73 Child tasks inherit counters.
76 Profile at this frequency.
80 Number of mmap data pages.
84 Do call-graph (stack chain/backtrace) recording.
88 Be more verbose (show counter open errors, etc).
104 Collect raw sample records from all opened counters (typically for tracepoint counters).
108 linkperf:perf-stat[1], linkperf:perf-list[1]