dev-manual, profile-manual: Removed oprofile section and link
Fixes [YOCTO #9264] I commented out a large section that had to do with running oprofile. Also, located and removed the link to that section from the profile-manual. (From yocto-docs rev: 63d6e754f994693c9a4d4b8211c6ef5f817c31f7) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
4f3dfa808c
commit
d94fa00ab5
|
@ -9604,6 +9604,7 @@
|
|||
</section>
|
||||
</section>
|
||||
|
||||
<!--
|
||||
<section id="platdev-oprofile">
|
||||
<title>Profiling with OProfile</title>
|
||||
|
||||
|
@ -9665,14 +9666,14 @@
|
|||
|
||||
<para>
|
||||
<literallayout class='monospaced'>
|
||||
# opcontrol --reset
|
||||
# opcontrol --start --separate=lib --no-vmlinux -c 5
|
||||
# opcontrol ‐‐reset
|
||||
# opcontrol ‐‐start ‐‐separate=lib ‐‐no-vmlinux -c 5
|
||||
.
|
||||
.
|
||||
[do whatever is being profiled]
|
||||
.
|
||||
.
|
||||
# opcontrol --stop
|
||||
# opcontrol ‐‐stop
|
||||
$ opreport -cl
|
||||
</literallayout>
|
||||
</para>
|
||||
|
@ -9685,7 +9686,7 @@
|
|||
five levels deep.
|
||||
<note>
|
||||
To profile the kernel, you would specify the
|
||||
<filename>--vmlinux=/path/to/vmlinux</filename> option.
|
||||
<filename>‐‐vmlinux=/path/to/vmlinux</filename> option.
|
||||
The <filename>vmlinux</filename> file is usually in the source directory in the
|
||||
<filename>/boot/</filename> directory and must match the running kernel.
|
||||
</note>
|
||||
|
@ -9748,7 +9749,7 @@
|
|||
With this connection, you just need to run "oprofile-server" on the device.
|
||||
By default, OProfile listens on port 4224.
|
||||
<note>
|
||||
You can change the port using the <filename>--port</filename> command-line
|
||||
You can change the port using the <filename>‐‐port</filename> command-line
|
||||
option.
|
||||
</note>
|
||||
</para>
|
||||
|
@ -9838,14 +9839,14 @@
|
|||
If network access to the target is unavailable, you can generate
|
||||
an archive for processing in <filename>oprofile-viewer</filename> as follows:
|
||||
<literallayout class='monospaced'>
|
||||
# opcontrol --reset
|
||||
# opcontrol --start --separate=lib --no-vmlinux -c 5
|
||||
# opcontrol ‐‐reset
|
||||
# opcontrol ‐‐start ‐‐separate=lib ‐‐no-vmlinux -c 5
|
||||
.
|
||||
.
|
||||
[do whatever is being profiled]
|
||||
.
|
||||
.
|
||||
# opcontrol --stop
|
||||
# opcontrol ‐‐stop
|
||||
# oparchive -o my_archive
|
||||
</literallayout>
|
||||
</para>
|
||||
|
@ -9860,6 +9861,7 @@
|
|||
</section>
|
||||
</section>
|
||||
</section>
|
||||
-->
|
||||
|
||||
<section id='maintaining-open-source-license-compliance-during-your-products-lifecycle'>
|
||||
<title>Maintaining Open Source License Compliance During Your Product's Lifecycle</title>
|
||||
|
|
|
@ -2746,8 +2746,7 @@
|
|||
Yocto already has some information on setting up and using
|
||||
OProfile and oprofileui. As this document doesn't cover
|
||||
everything in detail, it may be worth taking a look at the
|
||||
"<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-oprofile'>Profiling with OProfile</ulink>"
|
||||
section in the Yocto Project Development Manual
|
||||
Yocto Project Development Manual
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
Loading…
Reference in New Issue