English Portuguese (Brazil)
While using OProfile is suggested in cases of collecting data on where and why the processor spends time in a particular area of code, it is less usable when finding out why the processor stays idle.
You might want to use SystemTap when instrumenting specific places in code. Because SystemTap allows you to run the code instrumentation without having to stop and restart the instrumented code, it is particularly useful for instrumenting the kernel and daemons.
For more information on SystemTap, see xref:OProfile.adoc#br-oprofile_online_documentation[Online Documentation] for the relevant SystemTap documentation.
indexterm:[OProfile,additional resources] To learn more about OProfile and how to configure it, see the following resources.
.Installed Documentation
* `/usr/share/doc/oprofile/oprofile.html` — [citetitle]_OProfile Manual_
* `oprofile(1)` manual page — Discusses [command]#opcontrol#, [command]#opreport#, [command]#opannotate#, and [command]#ophelp#
* `operf(1)` manual page
.Online Documentation
* link:++http://oprofile.sourceforge.net/++[http://oprofile.sourceforge.net/] — Contains the latest upstream documentation, mailing lists, IRC channels, and more.
.See Also
* link:++https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SystemTap_Beginners_Guide/index.html++[SystemTap Beginners Guide] — Provides basic instructions on how to use SystemTap to monitor different subsystems of {MAJOROS} in finer detail.