mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
profile-manual: remove unused labels
(From yocto-docs rev: 4ee8a38f23f600fb9dac5d25bd884a195f7d72c0) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Nicolas Dechesne
committed by
Richard Purdie
Richard Purdie
parent
d54b7f2e00
commit
b3b5d2e0e0
@@ -4,8 +4,6 @@
|
||||
Yocto Project Profiling and Tracing Manual
|
||||
******************************************
|
||||
|
||||
.. _profile-intro:
|
||||
|
||||
Introduction
|
||||
============
|
||||
|
||||
@@ -30,8 +28,6 @@ The final section of this 'HOWTO' is a collection of real-world examples
|
||||
which we'll be continually adding to as we solve more problems using the
|
||||
tools - feel free to add your own examples to the list!
|
||||
|
||||
.. _profile-manual-general-setup:
|
||||
|
||||
General Setup
|
||||
=============
|
||||
|
||||
|
||||
@@ -10,8 +10,6 @@ Basic Usage (with examples) for each of the Yocto Tracing Tools
|
||||
This chapter presents basic usage examples for each of the tracing
|
||||
tools.
|
||||
|
||||
.. _profile-manual-perf:
|
||||
|
||||
perf
|
||||
====
|
||||
|
||||
@@ -43,8 +41,6 @@ want to apply the tool; full documentation can be found either within
|
||||
the tool itself or in the man pages at
|
||||
`perf(1) <http://linux.die.net/man/1/perf>`__.
|
||||
|
||||
.. _perf-setup:
|
||||
|
||||
Perf Setup
|
||||
----------
|
||||
|
||||
@@ -61,8 +57,6 @@ profile data and copy it to the host for analysis, but for the rest of
|
||||
this document we assume you've ssh'ed to the host and will be running
|
||||
the perf commands on the target.
|
||||
|
||||
.. _perf-basic-usage:
|
||||
|
||||
Basic Perf Usage
|
||||
----------------
|
||||
|
||||
@@ -950,8 +944,6 @@ We can look at the raw output using 'perf script' with no arguments: ::
|
||||
kworker/1:1 21 [001] 6171.470082: sched_switch: prev_comm=kworker/1:1 prev_pid=21 prev_prio=120 prev_state=S ==> next_comm=perf next_pid=1383 next_prio=120
|
||||
perf 1383 [001] 6171.480035: sched_wakeup: comm=kworker/1:1 pid=21 prio=120 success=1 target_cpu=001
|
||||
|
||||
.. _perf-filtering:
|
||||
|
||||
Filtering
|
||||
^^^^^^^^^
|
||||
|
||||
@@ -1138,8 +1130,6 @@ callgraphs from starting a few programs during those 30 seconds:
|
||||
uprobes. kprobes and uprobes are also used by and in fact are the
|
||||
main focus of SystemTap.
|
||||
|
||||
.. _perf-documentation:
|
||||
|
||||
Perf Documentation
|
||||
------------------
|
||||
|
||||
@@ -1182,8 +1172,6 @@ There's also a nice perf tutorial on the perf
|
||||
wiki that goes into more detail than we do here in certain areas: `Perf
|
||||
Tutorial <https://perf.wiki.kernel.org/index.php/Tutorial>`__
|
||||
|
||||
.. _profile-manual-ftrace:
|
||||
|
||||
ftrace
|
||||
======
|
||||
|
||||
@@ -1191,8 +1179,6 @@ ftrace
|
||||
this encompasses a number of related tracers along with the
|
||||
infrastructure that they all make use of.
|
||||
|
||||
.. _ftrace-setup:
|
||||
|
||||
ftrace Setup
|
||||
------------
|
||||
|
||||
@@ -1668,8 +1654,6 @@ trace-cmd and kernelshark in the next section.
|
||||
/sys/kernel/debug/tracing will be removed and replaced with
|
||||
equivalent tracers based on the 'trace events' subsystem.
|
||||
|
||||
.. _trace-cmd-kernelshark:
|
||||
|
||||
trace-cmd/kernelshark
|
||||
---------------------
|
||||
|
||||
@@ -1737,8 +1721,6 @@ The tool is pretty self-explanatory, but for more detailed information
|
||||
on navigating through the data, see the `kernelshark
|
||||
website <http://rostedt.homelinux.com/kernelshark/>`__.
|
||||
|
||||
.. _ftrace-documentation:
|
||||
|
||||
ftrace Documentation
|
||||
--------------------
|
||||
|
||||
@@ -1772,8 +1754,6 @@ There's more detailed documentation kernelshark usage here:
|
||||
An amusing yet useful README (a tracing mini-HOWTO) can be found in
|
||||
``/sys/kernel/debug/tracing/README``.
|
||||
|
||||
.. _profile-manual-systemtap:
|
||||
|
||||
systemtap
|
||||
=========
|
||||
|
||||
@@ -1835,8 +1815,6 @@ target system and 3) insert the module into the target kernel, which
|
||||
arms it, and 4) collect the data generated by the probe and display it
|
||||
to the user.
|
||||
|
||||
.. _systemtap-setup:
|
||||
|
||||
systemtap Setup
|
||||
---------------
|
||||
|
||||
@@ -1955,8 +1933,6 @@ no password):
|
||||
matchbox-termin(1036) open ("/tmp/vte3FS2LW", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600)
|
||||
matchbox-termin(1036) open ("/tmp/vteJMC7LW", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600)
|
||||
|
||||
.. _systemtap-documentation:
|
||||
|
||||
systemtap Documentation
|
||||
-----------------------
|
||||
|
||||
@@ -1967,8 +1943,6 @@ Links to other SystemTap documents, tutorials, and examples can be found
|
||||
here: `SystemTap documentation
|
||||
page <http://sourceware.org/systemtap/documentation.html>`__
|
||||
|
||||
.. _profile-manual-sysprof:
|
||||
|
||||
Sysprof
|
||||
=======
|
||||
|
||||
@@ -1976,8 +1950,6 @@ Sysprof is a very easy to use system-wide profiler that consists of a
|
||||
single window with three panes and a few buttons which allow you to
|
||||
start, stop, and view the profile from one place.
|
||||
|
||||
.. _sysprof-setup:
|
||||
|
||||
Sysprof Setup
|
||||
-------------
|
||||
|
||||
@@ -1990,8 +1962,6 @@ be running Sysprof on the target (you can use the '-X' option to ssh and
|
||||
have the Sysprof GUI run on the target but display remotely on the host
|
||||
if you want).
|
||||
|
||||
.. _sysprof-basic-usage:
|
||||
|
||||
Basic Sysprof Usage
|
||||
-------------------
|
||||
|
||||
@@ -2040,8 +2010,6 @@ to the selected function, and so on.
|
||||
the -g (--call-graph) option that you can experiment with; one of the
|
||||
options is 'caller' for an inverted caller-based callgraph display.
|
||||
|
||||
.. _sysprof-documentation:
|
||||
|
||||
Sysprof Documentation
|
||||
---------------------
|
||||
|
||||
@@ -2053,8 +2021,6 @@ Linux <http://sysprof.com/>`__
|
||||
LTTng (Linux Trace Toolkit, next generation)
|
||||
============================================
|
||||
|
||||
.. _lttng-setup:
|
||||
|
||||
LTTng Setup
|
||||
-----------
|
||||
|
||||
@@ -2239,8 +2205,6 @@ trace - it's still there in ~/lttng-traces): ::
|
||||
root@crownbay:~# lttng destroy
|
||||
Session auto-20190303-021943 destroyed at /home/root
|
||||
|
||||
.. _lltng-documentation:
|
||||
|
||||
LTTng Documentation
|
||||
-------------------
|
||||
|
||||
@@ -2254,8 +2218,6 @@ For information on LTTng in general, visit the `LTTng
|
||||
Project <http://lttng.org/lttng2.0>`__ site. You can find a "Getting
|
||||
Started" link on this site that takes you to an LTTng Quick Start.
|
||||
|
||||
.. _profile-manual-blktrace:
|
||||
|
||||
blktrace
|
||||
========
|
||||
|
||||
@@ -2264,8 +2226,6 @@ blktrace provides the tracing half of the equation; its output can be
|
||||
piped into the blkparse program, which renders the data in a
|
||||
human-readable form and does some basic analysis:
|
||||
|
||||
.. _blktrace-setup:
|
||||
|
||||
blktrace Setup
|
||||
--------------
|
||||
|
||||
@@ -2281,8 +2241,6 @@ collect and analyze the data on the host (see the
|
||||
below). For the rest of this section we assume you've ssh'ed to the host and
|
||||
will be running blkrace on the target.
|
||||
|
||||
.. _blktrace-basic-usage:
|
||||
|
||||
Basic blktrace Usage
|
||||
--------------------
|
||||
|
||||
@@ -2411,8 +2369,6 @@ I/O traffic during the run. You can look at the
|
||||
`blkparse <http://linux.die.net/man/1/blkparse>`__ manpage to learn the
|
||||
meaning of each field displayed in the trace listing.
|
||||
|
||||
.. _blktrace-live-mode:
|
||||
|
||||
Live Mode
|
||||
~~~~~~~~~
|
||||
|
||||
@@ -2603,8 +2559,6 @@ And this turns off tracing for the specified device: ::
|
||||
|
||||
root@crownbay:/sys/kernel/debug/tracing# echo 0 > /sys/block/sdc/trace/enable
|
||||
|
||||
.. _blktrace-documentation:
|
||||
|
||||
blktrace Documentation
|
||||
----------------------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user