OPROFILE(1)                General Commands Manual               OPROFILE(1)

NAME         top

       oprofile  - a statistical profiler for Linux systems, capable of pro‐
       filing all running code at low overhead; also included is  a  set  of
       post-profiling  analysis  tools,  as  well as a simple event counting

SYNOPSIS         top

       operf [ options ]
       ocount [ options ]
       opreport [ options ] [ profile specification ]
       opannotate [ options ] [ profile specification ]
       oparchive [ options ] [ profile specification ]
       opgprof [ options ] [ profile specification ]

DESCRIPTION         top

       OProfile is a profiling system for systems running Linux 2.6.31 and
       greater. OProfile makes use of the hardware performance counters
       provided on Intel, AMD, and other processors.  OProfile can profile a
       selected program or process or the whole system.  OProfile can also
       be used to collect cumulative event counts at the application,
       process, or system level.
       For a gentle guide to using OProfile, please read the HTML
       documentation listed in SEE ALSO.

OPERF         top

       operf is a performance profiler tool for Linux.

OCOUNT         top

       ocount is an event counting tool for Linux.

OPREPORT         top

       opreport gives image and symbol-based profile summaries for the whole
       system or a subset of binary images.

OPANNOTATE         top

       opannotate can produce annotated source or mixed source and assembly

OPARCHIVE         top

       oparchive produces oprofile archive for offline analysis

OPGPROF         top

       opgprof can produce a gprof-format profile for a single binary.


       Various optional profile specifications may be used with the post-
       profiling tools. A profile specification is some combination of the
       parameters listed below. ( Note: Enclosing part of a profile
       specification in curly braces { } can be used for differential
       profiles with opreport, but the braces must be surrounded by

              Path to the archive to inspect, as generated by oparchive

              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 'image:/usr/bin/operf,*op*,./oprofpp'

              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 excluded.

              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-

              Only consider profiles for the given numbered CPU (starting
              from zero).  This is only useful when using CPU profile

              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.

ENVIRONMENT         top

       No special environment variables are recognized by OProfile.

FILES         top

              OProfile user guide.

              Schema file for opreport XML output.

              Schema file for ophelp XML output.

              Event description files used by OProfile.

              The profiler log file.

              The location of the generated sample files.

VERSION         top

       This man page is current for oprofile-1.3.0git.

SEE ALSO         top

       /usr/local/share/doc/oprofile/, operf(1), ocount(1), opreport(1),
       opannotate(1), oparchive(1), opgprof(1), gprof(1), CPU vendor
       architecture manuals

COPYRIGHT         top

       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.

AUTHORS         top

       John Levon <> is the primary author. See the
       documentation for other contributors.

COLOPHON         top

       This page is part of the oprofile (a system-wide profiler for Linux)
       project.  Information about the project can be found at 
       ⟨⟩.  If you have a bug report for
       this manual page, see ⟨⟩.  This
       page was obtained from the project's upstream Git repository ⟨git⟩ on
       2017-09-15.  If you discover any rendering problems in this HTML ver‐
       sion of the page, or you believe there is a better or more up-to-date
       source for the page, or you have corrections or improvements to the
       information in this COLOPHON (which is not part of the original man‐
       ual page), send a mail to

4th Berkeley Distribution   Fri 15 September 2017                OPROFILE(1)

Pages that refer to this page: oparchive(1)opjitconv(1)lookup_dcookie(2)