English Spanish
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
Event Specifications
* `event` — The event to monitor.
Example Usage
Execute the following command to start profiling kernel mode for the counter again:
Execute the following command to start profiling user mode for the counter again:
* `extra` — Used on machines with Nehalem processors to further specify the event to monitor.
[[fig-oprofile-configuration]] .OProfile Configuration
[[fig-oprofile-setup]] .OProfile Setup
Find out which kernel is running with the [command]#uname -a# command, obtain the appropriate [package]*debuginfo* package and install it on the machine.
For more information on SystemTap, see xref:OProfile.adoc#br-oprofile_online_documentation[Online Documentation] for the relevant SystemTap documentation.
For this utility to work, the appropriate [package]*debuginfo* package for the executable must be installed on the system. On {MAJOROS}, the [package]*debuginfo* packages are not automatically installed with the corresponding packages that contain the executable. You have to obtain and install them separately.
Getting More Detailed Output on the Modules
Graphical Interface
Here, pass a comma-separated list of event specifications for profiling. Each event specification is a colon-separated list of attributes in the following form:
If any unit masks are available for the currently selected event, as discussed in xref:OProfile.adoc#s3-oprofile-events-unit-masks[Unit Masks], they are displayed in the `Unit Masks` area on the right side of the `Setup` tab. Select the check box beside the unit mask to enable it for the event.
If [option]`--separate=library` is used, the sample file name includes the name of the executable as well as the name of the library.
If `Per-application profiles` is selected, OProfile generates per-application profiles for libraries. This is equivalent to the [command]#opcontrol --separate=library# command. If `Per-application profiles, including kernel` is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in xref:OProfile.adoc#s2-oprofile-starting-separate[Separating Kernel and User-space Profiles]. This is equivalent to the [command]#opcontrol --separate=kernel# command.
If the `Verbose` option is selected, the [command]#oprofiled# daemon log includes more detailed information.
If `timer` is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than 0 are not set to an event by default. The default events monitored are shown in xref:OProfile.adoc#tb-oprofile-default-events[Default Events].