English Persian
Using log file /var/lib/oprofile/oprofiled.log Daemon started. Profiler running.
Using [command]#opreport#
Using [command]#operf# in System-wide Mode
Using [command]#opannotate#
Use xref:OProfile.adoc#tb-oprofile-processors[OProfile Processors and Counters] to determine the number of events that can be monitored simultaneously for your CPU type. If the processor does not have supported performance monitoring hardware, the `timer` is used as the processor type.
Use these tools, along with the binaries profiled, to generate reports that can be further analyzed.
Use the `Count` text field to set the sampling rate for the currently selected event as discussed in xref:OProfile.adoc#s3-oprofile-events-sampling[Sampling Rate].
* `user` — If 0, samples are not collected for the counter event when the processor is in user-space; if 1, samples are collected even if the processor is in user-space.
*Use of shared libraries* — Samples for code in shared libraries are not attributed to the particular application unless the [option]`--separate=library` option is used.
Unless OProfile is properly configured, [command]#ophelp# fails with the following error message:
Unit masks for each event are listed with the [command]#ophelp# command. The values for each unit mask are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal values must be combined using a bitwise _or_ operation.
Unit Masks
* `unit_mask` — Defines which unit masks are enabled for the counter.
Understanding the /dev/oprofile/ directory
Unable to open cpu_type file for reading
Make sure you have done opcontrol --init
cpu_type 'unset' is not valid
you should upgrade oprofile or force the use of timer mode
To stop the profiler, execute the following command as root:
To start the monitoring process, for example, on a machine with Westmere processor, run the following command:
To start OProfile from the graphical interface, click btn:[Start]. To stop the profiler, click btn:[Stop]. Exiting the application does not stop OProfile from sampling.
To specify the session directory to hold the sample data, use the [option]`--session-dir` option. If not specified, the data is saved in the `oprofile_data/` directory on the current path.
To set the event for each configurable counter via the command line, use [command]#opcontrol#: