mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 12:59:02 +02:00
11c048fbea
All filenames duplicate the 'manual name', which is not needed, and make all references longer than they should. Rename all files to be as consise as possible, and fix all references (From yocto-docs rev: 44405490888960208058d016e387507e21c9f478) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
30 lines
1.0 KiB
ReStructuredText
30 lines
1.0 KiB
ReStructuredText
.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
|
|
|
|
*************************************************************
|
|
Overall Architecture of the Linux Tracing and Profiling Tools
|
|
*************************************************************
|
|
|
|
Architecture of the Tracing and Profiling Tools
|
|
===============================================
|
|
|
|
It may seem surprising to see a section covering an 'overall
|
|
architecture' for what seems to be a random collection of tracing tools
|
|
that together make up the Linux tracing and profiling space. The fact
|
|
is, however, that in recent years this seemingly disparate set of tools
|
|
has started to converge on a 'core' set of underlying mechanisms:
|
|
|
|
- static tracepoints
|
|
- dynamic tracepoints
|
|
|
|
- kprobes
|
|
- uprobes
|
|
|
|
- the perf_events subsystem
|
|
- debugfs
|
|
|
|
.. admonition:: Tying it Together
|
|
|
|
Rather than enumerating here how each tool makes use of these common
|
|
mechanisms, textboxes like this will make note of the specific usages
|
|
in each tool as they come up in the course of the text.
|