English Persian
Each directory for a counter contains the following files:
Each executable is listed on its own line. The first column is the number of samples recorded for the executable. The second column is the percentage of samples relative to the total number of samples. The third column is the name of the executable.
Each sample file name is based on the name of the executable. For example, the samples for the default event on a Pentium III processor for [command]#/bin/bash# becomes:
~]# echo 0 > /proc/sys/kernel/nmi_watchdog
~]# echo 1 > /proc/sys/kernel/nmi_watchdog
* `enabled` — If 0, the counter is off and no samples are collected for it; if 1, the counter is on and samples are being collected for it.
_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