sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Read-thru edits to "Profiling with OProfile" 

Minor edits.

(From yocto-docs rev: 551127f3afa65f36bf9baf21d0ca3e53a2fbb3c1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-03-19 08:30:01 -06:00 committed by Richard Purdie
parent 46330cd0bc
commit c70b6e8a42
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -6487,23 +6487,23 @@
This profiler provides answers to questions like "Which functions does my application spend
the most time in when doing X?"
Because the OpenEmbedded build system is well integrated with OProfile, it makes profiling
applications on target hardware straightforward.
applications on target hardware straight forward.
<note>
For more information on how to set up and run OProfile, see the
"<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>OProfile</ulink>"
"<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>oprofile</ulink>"
section in the Yocto Project Profiling and Tracing Manual.
</note>
</para>
<para>
To use OProfile, you need an image that has OProfile installed.
The easiest way to do this is with <filename>tools-profile</filename> in the
The easiest way to do this is with "tools-profile" in the
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FEATURES'>IMAGE_FEATURES</ulink></filename> variable.
You also need debugging symbols to be available on the system where the analysis
takes place.
You can gain access to the symbols by using <filename>dbg-pkgs</filename> in the
You can gain access to the symbols by using "dbg-pkgs" in the
<filename>IMAGE_FEATURES</filename> variable or by
installing the appropriate <filename>-dbg</filename> packages.
installing the appropriate DBG (<filename>-dbg</filename>) packages.
</para>
<para>
@ -6531,7 +6531,7 @@
<title>Profiling on the Target</title>
<para>
Using OProfile you can perform all the profiling work on the target device.
Using OProfile, you can perform all the profiling work on the target device.
A simple OProfile session might look like the following:
</para>
@ -6627,7 +6627,7 @@
<para>
The client program is called <filename>oprofile-viewer</filename> and its UI is relatively
straightforward.
straight forward.
You access key functionality through the buttons on the toolbar, which
are duplicated in the menus.
Here are the buttons:
@ -6657,7 +6657,7 @@
</para>
<para>
The client downloads the complete 'profile archive' from
The client downloads the complete profile archive from
the target to the host for processing.
This archive is a directory that contains the sample data, the object files,
and the debug information for the object files.
@ -6695,9 +6695,9 @@
All that is needed is a copy of the filesystem with the debug symbols present
on the viewer system.
The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launch GDB on the Host Computer</link>"
section covers how to create such a directory with
the <link linkend='source-directory'>Source Directory</link>
and how to use the OProfileUI Settings Dialog to specify the location.
section covers how to create such a directory within
the source directory and how to use the OProfileUI Settings
Dialog to specify the location.
If you specify the directory, it will be used when the file checksums
match those on the system you are profiling.
</para>