oprofile - a system-wide profiler
opcontrol [ options ]
opreport [ options ] [ profile specification ]
opstack [ options ] [ profile specification ]
opannotate [ options ] [ profile specification ]
oparchive [ options ] [ profile specification ]
opgprof [ options ] [ profile specification ]
OProfile is a profiling system for systems running Linux 2.2, 2.4, and
2.6. Profiling runs transparently in the background and profile data
can be collected at any time. OProfile makes use of the hardware per-
formance counters provided on Intel, AMD, and other processors, and
uses a timer-interrupt based mechanism on CPUs without counters. OPro-
file can profile the whole system in high detail.
For a gentle guide to using OProfile, please read the HTML documenta-
tion listed in SEE ALSO.
opcontrol is used for starting and stopping the OProfile daemon, and
providing set-up parameters.
opreport gives image and symbol-based profile summaries for the whole
system or a subset of binary images.
opstack reports call-graph profile summaries, if call-graph profiling
opannotate can produce annotated source or mixed source and assembly
oparchive produces oprofile archive for offline analysis
opgprof can produce a gprof-format profile for a single binary.
All of the post-profiling tools can take profile specifications, which
is some combination of the following parameters.
A comma-separated list of session names to resolve in. Absence
of this tag, unlike all others, means "the current session",
equivalent to specifying "session:current".
A comma-separated list of sessions to exclude.
A comma-separated list of image names to resolve. Each entry may
be relative path, glob-style name, or full path, e.g. opreport
Same as image:, but the matching images are excluded.
Same as image:, but only for images that are for a particular
primary binary image (namely, an application). This only makes
sense to use if you’re using --separate. This includes kernel
modules and the kernel when using --separate=kernel.
Same as <option>lib-image:</option>, but the matching images are
The symbolic event name to match on, e.g. event:DATA_MEM_REFS.
The event count to match on, e.g. event:DATA_MEM_REFS
The unit mask value of the event to match on, e.g. unit-mask:1.
Only consider profiles for the given numbered CPU (starting from
zero). This is only useful when using CPU profile separation.
Only consider profiles for the given task groups. Unless some
program is using threads, the task group ID of a process is the
same as its process ID. This option corresponds to the POSIX
notion of a thread group. This is only useful when using per-
process profile separation.
Only consider profiles for the given threads. When using recent
thread libraries, all threads in a process share the same task
group ID, but have different thread IDs. You can use this option
in combination with tgid: to restrict the results to particular
threads within a process. This is only useful when using per-
process profile separation.
No special environment variables are recognised by oprofile.
Configuration file for opcontrol
Event description files used by OProfile.
The user-space daemon logfile.
/var/lib/oprofile/opdev, /var/lib/oprofile/ophashmapdev, /var/lib/opro-
The device files for communication with the Linux 2.4 kernel
The device filesystem for communication with the Linux 2.6 ker-
The location of the generated sample files.
This man page is current for oprofile-0.8.2.
/usr/share/doc/oprofile/, opcontrol(1), opreport(1), opstack(1), opan-
notate(1), oparchive(1), opgprof(1), gprof(1), readprofile(1), CPUven-
oprofile is Copyright (C) 1998-2004 University of Manchester, UK, John
Levon, and others. OProfile is released under the GNU General Public
License, Version 2, or (at your option) any later version.
John Levon <firstname.lastname@example.org> is the primary author. See the
documentation for other contributors.
4th Berkeley Distribution Wed 13 April 2005 OPROFILE(1)
Man(1) output converted with