Linux Blog


Section: User Commands (1)
Updated: Sun 24 June 2007
Index Return to Main Contents


opcontrol - control OProfile profiling  


opcontrol [ options ]  


opcontrol can be used to start profiling, end a profiling session, dump profile data, and set up the profiling parameters.



Show help message.
Show version.
Shows the monitorable events.
Load the OProfile module if required and make the OProfile driver interface available.
Followed by list options for profiling setup. Store setup in ~root/.oprofile/daemonrc. Optional.
Show configuration information.
Start the oprofile daemon without starting profiling. Not available in 2.2/2.4 kernels.
Start data collection with either arguments provided by --setup or with information saved in ~root/.oprofile/daemonrc.
Force a flush of the collected profiling data to the daemon.
Stop data collection. Not available in 2.2/2.4 kernels.
Stop data collection and kill the daemon.
Clear out data from current session, but leaves saved sessions.
Save data from current session to sessionname.
Shut down daemon. Unload the oprofile module and oprofilefs.
Set kernel buffer to num samples. When using a 2.6 kernel buffer watershed need to be tweaked when changing this value.
Set kernel buffer watershed to num samples (2.6 only). When it'll remain only buffer-size - buffer-watershed free entry in the kernel buffer data will be flushed to daemon, most usefull value are in the range [0.25 - 0.5] * buffer-size.
Set kernel per cpu buffer to num samples (2.6 only). If you profile at high rate it can help to increase this if the log file show excessive count of sample lost cpu buffer overflow.
Add an event to measure for the hardware performance counters, or "default" for the default event. The event is of the form "CPU_CLK_UNHALTED:30000:0:1:1" where the numeric values are count, unit mask, kernel-space counting, user-space counting, respectively.
Separate samples based on the given separator. 'lib' separates dynamically linked library samples per application. 'kernel' separates kernel and kernel module samples per application; 'kernel' implies 'library'. 'thread' gives separation for each thread and task. 'cpu' separates for each CPU. 'all' implies all of the above options and 'none' turns off separation.
Enable callgraph sample collection with a maximum depth. Use 0 to disable callgraph profiling. This option is currently only usable on x86, using a 2.6+ kernel with callgraph support enabled.
Only profile the given absolute paths to binaries, or "all" to profile everything (the default).
vmlinux kernel image.
Use this when you don't have a kernel vmlinux file, and you don't want to profile the kernel.
Be verbose in the daemon log. This has a high overhead.
Set kernel range vma address in hexadecimal.


OPTIONS (specific to Xen)

Xen image
List of domain ids participating in a multi-domain profiling session. If more than one domain is specified in <list> they should be separated using commas. This option can only be used in domain 0 which is the only domain that can coordinate a multi-domain profiling session. Including domain 0 in the list of active domains is optional. (e.g. --active-domains=2,5,6 and --active-domains=0,2,5,6 are equivalent)



No special environment variables are recognised by opcontrol.



Configuration file for opcontrol
The location of the generated sample files.



This man page is current for oprofile-0.9.2.



/usr/share/doc/oprofile/, oprofile(1)



OPTIONS (specific to Xen)

Random Man Pages: