Este contenido no está disponible en el idioma seleccionado.
29.2.3. Separating Kernel and User-space Profiles
By default, kernel mode and user mode information is gathered for each event. To configure OProfile to ignore events in kernel mode for a specific counter, execute the following command:
~]# opcontrol --event=event-name:sample-rate:unit-mask:0
Execute the following command to start profiling kernel mode for the counter again:
~]# opcontrol --event=event-name:sample-rate:unit-mask:1
To configure OProfile to ignore events in user mode for a specific counter, execute the following command:
~]# opcontrol --event=event-name:sample-rate:unit-mask:kernel:0
Execute the following command to start profiling user mode for the counter again:
~]# opcontrol --event=event-name:sample-rate:unit-mask:kernel:1
When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root:
~]# opcontrol --separate=choice
choice can be one of the following:
none— Do not separate the profiles (default).library— Generate per-application profiles for libraries.kernel— Generate per-application profiles for the kernel and kernel modules.all— Generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules.
If
--separate=library is used, the sample file name includes the name of the executable as well as the name of the library.
Note
These configuration changes will take effect when the OProfile profiler is restarted.
