From eb8dc40360f0cfef56fb6947cc817a547d6d9bc6 Mon Sep 17 00:00:00 2001 From: Dave Cobbley Date: Tue, 14 Aug 2018 10:05:37 -0700 Subject: [Subtree] Removing import-layers directory As part of the move to subtrees, need to bring all the import layers content to the top level. Change-Id: I4a163d10898cbc6e11c27f776f60e1a470049d8f Signed-off-by: Dave Cobbley Signed-off-by: Brad Bishop --- .../profile-manual/profile-manual-arch.xml | 45 ++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 poky/documentation/profile-manual/profile-manual-arch.xml (limited to 'poky/documentation/profile-manual/profile-manual-arch.xml') diff --git a/poky/documentation/profile-manual/profile-manual-arch.xml b/poky/documentation/profile-manual/profile-manual-arch.xml new file mode 100644 index 000000000..19d115522 --- /dev/null +++ b/poky/documentation/profile-manual/profile-manual-arch.xml @@ -0,0 +1,45 @@ + %poky; ] > + + + +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 + + + + + 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. + +
+
+ -- cgit v1.2.3