|File Search||Catalog||Content Search|
OProfile leverages the hardware performance counters of the CPU to enable profiling of a wide variety of interesting statistics, which can also be used for basic time-spent profiling. All code is profiled: hardware and software interrupt handlers, kernel modules, the kernel, shared libraries, and applications (the only exception being the OProfile interrupt handler itself). Note that different architectures can use different hardware mechanisms to collect data.
OProfile is currently in alpha status; however it has proven stable over a large number of differing configurations. As always, there is no warranty.
This is an alpha release version of oprofile, a transparent low-overhead system-wide profiler. You can find some documentation in the doc/ directory. Please visit the oprofile website at : http://oprofile.sf.net/ oprofile was written by John Levon <firstname.lastname@example.org> and Philippe Elie <email@example.com>. Maynard Johnson <firstname.lastname@example.org> is the current maintainer. Dave Jones <dave more»
OPANNOTATE(1) OPANNOTATE(1) NAME opannotate - produce source or assembly annotated with pro‐ file data SYNOPSIS opannotate [ options ] [profile specification] DESCRIPTION opannotate outputs annotated source and/or assembly from pro‐ file data of an OProfile session. See oprofile(1) for how to write profi more»
OPARCHIVE(1) OPARCHIVE(1) NAME oparchive - produce archive of oprofile data for offline analysis SYNOPSIS oparchive [ options ] [profile specification] -o [directory] DESCRIPTION oparchive generates a directory populated with executable, debug, and oprofile sample files. This directory can be move to more»
OPCONTROL(1) OPCONTROL(1) NAME opcontrol - cont more»
OPGPROF(1) OPGPROF(1) NAME opgprof - produc more»
OPHELP(1) OPHELP(1) NAME ophelp - list OP more»
OPIMPORT(1) OPIMPORT(1) NAME opimport - conve more»
OPREPORT(1) OPREPORT(1) NAME opreport - produ more»