summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-03-19 14:30:01 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-25 12:29:43 (GMT)
commitc70b6e8a426d884da1b6d24a1dc95be0cee5f8a7 (patch)
tree0604fde334554f79eb36c705001c17a2289a2519
parent46330cd0bc16449024e4c01b5c6ff15a1eb0612e (diff)
downloadpoky-c70b6e8a426d884da1b6d24a1dc95be0cee5f8a7.tar.gz
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>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 0f8df85..871f0a0 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -6487,23 +6487,23 @@
6487 This profiler provides answers to questions like "Which functions does my application spend 6487 This profiler provides answers to questions like "Which functions does my application spend
6488 the most time in when doing X?" 6488 the most time in when doing X?"
6489 Because the OpenEmbedded build system is well integrated with OProfile, it makes profiling 6489 Because the OpenEmbedded build system is well integrated with OProfile, it makes profiling
6490 applications on target hardware straightforward. 6490 applications on target hardware straight forward.
6491 <note> 6491 <note>
6492 For more information on how to set up and run OProfile, see the 6492 For more information on how to set up and run OProfile, see the
6493 "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>OProfile</ulink>" 6493 "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>oprofile</ulink>"
6494 section in the Yocto Project Profiling and Tracing Manual. 6494 section in the Yocto Project Profiling and Tracing Manual.
6495 </note> 6495 </note>
6496 </para> 6496 </para>
6497 6497
6498 <para> 6498 <para>
6499 To use OProfile, you need an image that has OProfile installed. 6499 To use OProfile, you need an image that has OProfile installed.
6500 The easiest way to do this is with <filename>tools-profile</filename> in the 6500 The easiest way to do this is with "tools-profile" in the
6501 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FEATURES'>IMAGE_FEATURES</ulink></filename> variable. 6501 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FEATURES'>IMAGE_FEATURES</ulink></filename> variable.
6502 You also need debugging symbols to be available on the system where the analysis 6502 You also need debugging symbols to be available on the system where the analysis
6503 takes place. 6503 takes place.
6504 You can gain access to the symbols by using <filename>dbg-pkgs</filename> in the 6504 You can gain access to the symbols by using "dbg-pkgs" in the
6505 <filename>IMAGE_FEATURES</filename> variable or by 6505 <filename>IMAGE_FEATURES</filename> variable or by
6506 installing the appropriate <filename>-dbg</filename> packages. 6506 installing the appropriate DBG (<filename>-dbg</filename>) packages.
6507 </para> 6507 </para>
6508 6508
6509 <para> 6509 <para>
@@ -6531,7 +6531,7 @@
6531 <title>Profiling on the Target</title> 6531 <title>Profiling on the Target</title>
6532 6532
6533 <para> 6533 <para>
6534 Using OProfile you can perform all the profiling work on the target device. 6534 Using OProfile, you can perform all the profiling work on the target device.
6535 A simple OProfile session might look like the following: 6535 A simple OProfile session might look like the following:
6536 </para> 6536 </para>
6537 6537
@@ -6627,7 +6627,7 @@
6627 6627
6628 <para> 6628 <para>
6629 The client program is called <filename>oprofile-viewer</filename> and its UI is relatively 6629 The client program is called <filename>oprofile-viewer</filename> and its UI is relatively
6630 straightforward. 6630 straight forward.
6631 You access key functionality through the buttons on the toolbar, which 6631 You access key functionality through the buttons on the toolbar, which
6632 are duplicated in the menus. 6632 are duplicated in the menus.
6633 Here are the buttons: 6633 Here are the buttons:
@@ -6657,7 +6657,7 @@
6657 </para> 6657 </para>
6658 6658
6659 <para> 6659 <para>
6660 The client downloads the complete 'profile archive' from 6660 The client downloads the complete profile archive from
6661 the target to the host for processing. 6661 the target to the host for processing.
6662 This archive is a directory that contains the sample data, the object files, 6662 This archive is a directory that contains the sample data, the object files,
6663 and the debug information for the object files. 6663 and the debug information for the object files.
@@ -6695,9 +6695,9 @@
6695 All that is needed is a copy of the filesystem with the debug symbols present 6695 All that is needed is a copy of the filesystem with the debug symbols present
6696 on the viewer system. 6696 on the viewer system.
6697 The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launch GDB on the Host Computer</link>" 6697 The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launch GDB on the Host Computer</link>"
6698 section covers how to create such a directory with 6698 section covers how to create such a directory within
6699 the <link linkend='source-directory'>Source Directory</link> 6699 the source directory and how to use the OProfileUI Settings
6700 and how to use the OProfileUI Settings Dialog to specify the location. 6700 Dialog to specify the location.
6701 If you specify the directory, it will be used when the file checksums 6701 If you specify the directory, it will be used when the file checksums
6702 match those on the system you are profiling. 6702 match those on the system you are profiling.
6703 </para> 6703 </para>