PERF\-RECORDSection: Misc. Reference Manual Pages (1)
Index Return to Main Contents
NAMEperf-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.
- 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.
- Event filter.
- 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. Must be a power of two.
- Do call-graph (stack chain/backtrace) recording.
- Doncqt print any message, useful for scripting.
- Be more verbose (show counter open errors, etc).
- Per thread counts.
- Sample addresses.
- Sample timestamps. Use it with perf report -D to see the timestamps, for instance.
- Doncqt sample.
- Collect raw sample records from all opened counters (default for tracepoint counters).
- 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 CPUs.
- 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.
-G name,..., --cgroup name,...
- monitor only in the container (cgroup) called "name". This option is available only in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to container "name" are monitored when they run on the monitored CPUs. Multiple cgroups can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup to first event, second cgroup to second event and so on. It is possible to provide an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have corresponding events, i.e., they always refer to events defined earlier on the command line.
This document was created by man2html, using the manual pages.
Time: 05:29:07 GMT, December 24, 2015