summaryrefslogtreecommitdiffstats
path: root/documentation/profile-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-01-21 22:15:27 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-27 13:56:04 (GMT)
commitb4b1dc1dd6014c2475777a54a4d5f8c2a2ec1961 (patch)
tree675cc57648aa60f35c68f618e7b9e0b99639de51 /documentation/profile-manual
parentf3cb97769994a3c288994a1cc42da0d4320aef81 (diff)
downloadpoky-b4b1dc1dd6014c2475777a54a4d5f8c2a2ec1961.tar.gz
profile-manual: Fixed the "Tying it Together" side-lights.
Took them out of the colored Note format and replaced with a simple line box to set them apart. (From yocto-docs rev: 5efb84d3860d87f64371b718967ab33f47a3a4db) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/profile-manual')
-rw-r--r--documentation/profile-manual/profile-manual-arch.xml6
-rw-r--r--documentation/profile-manual/profile-manual-usage.xml72
2 files changed, 39 insertions, 39 deletions
diff --git a/documentation/profile-manual/profile-manual-arch.xml b/documentation/profile-manual/profile-manual-arch.xml
index a0ea3b2..19d1155 100644
--- a/documentation/profile-manual/profile-manual-arch.xml
+++ b/documentation/profile-manual/profile-manual-arch.xml
@@ -32,12 +32,12 @@
32 </itemizedlist> 32 </itemizedlist>
33 </para> 33 </para>
34 34
35 <note> 35 <informalexample>
36 Tying It Together: Rather than enumerating here how each tool makes use of 36 <emphasis>Tying it Together:</emphasis> Rather than enumerating here how each tool makes use of
37 these common mechanisms, textboxes like this will make note of the 37 these common mechanisms, textboxes like this will make note of the
38 specific usages in each tool as they come up in the course 38 specific usages in each tool as they come up in the course
39 of the text. 39 of the text.
40 </note> 40 </informalexample>
41</section> 41</section>
42</chapter> 42</chapter>
43<!-- 43<!--
diff --git a/documentation/profile-manual/profile-manual-usage.xml b/documentation/profile-manual/profile-manual-usage.xml
index 785fd5c..e49acbf 100644
--- a/documentation/profile-manual/profile-manual-usage.xml
+++ b/documentation/profile-manual/profile-manual-usage.xml
@@ -605,13 +605,13 @@
605 </literallayout> 605 </literallayout>
606 </para> 606 </para>
607 607
608 <note> 608 <informalexample>
609 Tying It Together: These are exactly the same set of events defined 609 <emphasis>Tying it Together:</emphasis> These are exactly the same set of events defined
610 by the trace event subsystem and exposed by 610 by the trace event subsystem and exposed by
611 ftrace/tracecmd/kernelshark as files in 611 ftrace/tracecmd/kernelshark as files in
612 /sys/kernel/debug/tracing/events, by SystemTap as 612 /sys/kernel/debug/tracing/events, by SystemTap as
613 kernel.trace("tracepoint_name") and (partially) accessed by LTTng. 613 kernel.trace("tracepoint_name") and (partially) accessed by LTTng.
614 </note> 614 </informalexample>
615 615
616 <para> 616 <para>
617 Only a subset of these would be of interest to us when looking at 617 Only a subset of these would be of interest to us when looking at
@@ -836,8 +836,8 @@
836 bindings, one for Python and one for Perl. 836 bindings, one for Python and one for Perl.
837 </para> 837 </para>
838 838
839 <note> 839 <informalexample>
840 Tying It Together: Language bindings for manipulating and 840 <emphasis>Tying it Together:</emphasis> Language bindings for manipulating and
841 aggregating trace data are of course not a new 841 aggregating trace data are of course not a new
842 idea. One of the first projects to do this was IBM's DProbes 842 idea. One of the first projects to do this was IBM's DProbes
843 dpcc compiler, an ANSI C compiler which targeted a low-level 843 dpcc compiler, an ANSI C compiler which targeted a low-level
@@ -849,7 +849,7 @@
849 in-kernel interpreter, created an elaborate compiler-based 849 in-kernel interpreter, created an elaborate compiler-based
850 machinery to translate its language into kernel modules written 850 machinery to translate its language into kernel modules written
851 in C. 851 in C.
852 </note> 852 </informalexample>
853 853
854 <para> 854 <para>
855 Now that we have the trace data in perf.data, we can use 855 Now that we have the trace data in perf.data, we can use
@@ -1132,15 +1132,15 @@
1132 how to use filters, it's close enough. 1132 how to use filters, it's close enough.
1133 </para> 1133 </para>
1134 1134
1135 <note> 1135 <informalexample>
1136 Tying It Together: These are exactly the same set of event 1136 <emphasis>Tying it Together:</emphasis> These are exactly the same set of event
1137 filters defined by the trace event subsystem. See the 1137 filters defined by the trace event subsystem. See the
1138 ftrace/tracecmd/kernelshark section for more discussion about 1138 ftrace/tracecmd/kernelshark section for more discussion about
1139 these event filters. 1139 these event filters.
1140 </note> 1140 </informalexample>
1141 1141
1142 <note> 1142 <informalexample>
1143 Tying It Together: These event filters are implemented by a 1143 <emphasis>Tying it Together:</emphasis> These event filters are implemented by a
1144 special-purpose pseudo-interpreter in the kernel and are an 1144 special-purpose pseudo-interpreter in the kernel and are an
1145 integral and indispensable part of the perf design as it 1145 integral and indispensable part of the perf design as it
1146 relates to tracing. kernel-based event filters provide a 1146 relates to tracing. kernel-based event filters provide a
@@ -1161,7 +1161,7 @@
1161 application is causing buffer I/O overruns, it probably 1161 application is causing buffer I/O overruns, it probably
1162 means that you aren't taking enough advantage of the 1162 means that you aren't taking enough advantage of the
1163 kernel filtering engine. 1163 kernel filtering engine.
1164 </note> 1164 </informalexample>
1165 </section> 1165 </section>
1166 </section> 1166 </section>
1167 1167
@@ -1274,18 +1274,18 @@
1274 <imagedata fileref="figures/perf-probe-do_fork-profile.png" width="6in" depth="7in" align="center" scalefit="1" /> 1274 <imagedata fileref="figures/perf-probe-do_fork-profile.png" width="6in" depth="7in" align="center" scalefit="1" />
1275 </para> 1275 </para>
1276 1276
1277 <note> 1277 <informalexample>
1278 Tying It Together: The trace events subsystem accomodate static 1278 <emphasis>Tying it Together:</emphasis> The trace events subsystem accomodate static
1279 and dynamic tracepoints in exactly the same way - there's no 1279 and dynamic tracepoints in exactly the same way - there's no
1280 difference as far as the infrastructure is concerned. See the 1280 difference as far as the infrastructure is concerned. See the
1281 ftrace section for more details on the trace event subsystem. 1281 ftrace section for more details on the trace event subsystem.
1282 </note> 1282 </informalexample>
1283 1283
1284 <note> 1284 <informalexample>
1285 Tying It Together: Dynamic tracepoints are implemented under the 1285 <emphasis>Tying it Together:</emphasis> Dynamic tracepoints are implemented under the
1286 covers by kprobes and uprobes. kprobes and uprobes are also used 1286 covers by kprobes and uprobes. kprobes and uprobes are also used
1287 by and in fact are the main focus of SystemTap. 1287 by and in fact are the main focus of SystemTap.
1288 </note> 1288 </informalexample>
1289 </section> 1289 </section>
1290 </section> 1290 </section>
1291 1291
@@ -1496,10 +1496,10 @@
1496 code works in a dynamic sense. 1496 code works in a dynamic sense.
1497 </para> 1497 </para>
1498 1498
1499 <note> 1499 <informalexample>
1500 Tying It Together: The ftrace function tracer is also 1500 <emphasis>Tying it Together:</emphasis> The ftrace function tracer is also
1501 available from within perf, as the ftrace:function tracepoint. 1501 available from within perf, as the ftrace:function tracepoint.
1502 </note> 1502 </informalexample>
1503 1503
1504 <para> 1504 <para>
1505 It is a little more difficult to follow the call chains than 1505 It is a little more difficult to follow the call chains than
@@ -1852,21 +1852,21 @@
1852 including trace-cmd and kernelshark in the next section. 1852 including trace-cmd and kernelshark in the next section.
1853 </para> 1853 </para>
1854 1854
1855 <note> 1855 <informalexample>
1856 Tying It Together: These tracepoints and their representation 1856 <emphasis>Tying it Together:</emphasis> These tracepoints and their representation
1857 are used not only by ftrace, but by many of the other tools 1857 are used not only by ftrace, but by many of the other tools
1858 covered in this document and they form a central point of 1858 covered in this document and they form a central point of
1859 integration for the various tracers available in Linux. 1859 integration for the various tracers available in Linux.
1860 They form a central part of the instrumentation for the 1860 They form a central part of the instrumentation for the
1861 following tools: perf, lttng, ftrace, blktrace and SystemTap 1861 following tools: perf, lttng, ftrace, blktrace and SystemTap
1862 </note> 1862 </informalexample>
1863 1863
1864 <note> 1864 <informalexample>
1865 Tying It Together: Eventually all the special-purpose tracers 1865 <emphasis>Tying it Together:</emphasis> Eventually all the special-purpose tracers
1866 currently available in /sys/kernel/debug/tracing will be 1866 currently available in /sys/kernel/debug/tracing will be
1867 removed and replaced with equivalent tracers based on the 1867 removed and replaced with equivalent tracers based on the
1868 'trace events' subsystem. 1868 'trace events' subsystem.
1869 </note> 1869 </informalexample>
1870 </section> 1870 </section>
1871 1871
1872 <section id='trace-cmd-kernelshark'> 1872 <section id='trace-cmd-kernelshark'>
@@ -2731,14 +2731,14 @@
2731 <imagedata fileref="figures/oprofileui-busybox.png" width="6in" depth="7in" align="center" scalefit="1" /> 2731 <imagedata fileref="figures/oprofileui-busybox.png" width="6in" depth="7in" align="center" scalefit="1" />
2732 </para> 2732 </para>
2733 2733
2734 <note> 2734 <informalexample>
2735 Tying It Together: oprofile does have build options to enable 2735 <emphasis>Tying it Together:</emphasis> oprofile does have build options to enable
2736 use of the perf_event subsystem and benefit from the perf_event 2736 use of the perf_event subsystem and benefit from the perf_event
2737 infrastructure by adding support for something other than 2737 infrastructure by adding support for something other than
2738 system-wide profiling i.e. per-process or workload profiling, 2738 system-wide profiling i.e. per-process or workload profiling,
2739 but the version in danny doesn't yet take advantage of 2739 but the version in danny doesn't yet take advantage of
2740 those capabilities. 2740 those capabilities.
2741 </note> 2741 </informalexample>
2742 </section> 2742 </section>
2743 2743
2744 <section id='oprofile-documentation'> 2744 <section id='oprofile-documentation'>
@@ -2852,23 +2852,23 @@
2852 focus to the selected function, and so on. 2852 focus to the selected function, and so on.
2853 </para> 2853 </para>
2854 2854
2855 <note> 2855 <informalexample>
2856 Tying It Together: If you like sysprof's 'caller-oriented' 2856 <emphasis>Tying it Together:</emphasis> If you like sysprof's 'caller-oriented'
2857 display, you may be able to approximate it in other tools as 2857 display, you may be able to approximate it in other tools as
2858 well. For example, 'perf report' has the -g (--call-graph) 2858 well. For example, 'perf report' has the -g (--call-graph)
2859 option that you can experiment with; one of the options is 2859 option that you can experiment with; one of the options is
2860 'caller' for an inverted caller-based callgraph display. 2860 'caller' for an inverted caller-based callgraph display.
2861 </note> 2861 </informalexample>
2862 2862
2863 <note> 2863 <informalexample>
2864 Tying It Together: sysprof does have build options to enable 2864 <emphasis>Tying it Together:</emphasis> sysprof does have build options to enable
2865 use of the perf_event subsystem and benefit from the perf_event 2865 use of the perf_event subsystem and benefit from the perf_event
2866 infrastructure by adding support for something other than 2866 infrastructure by adding support for something other than
2867 system-wide profiling i.e. per-process or workload profiling, 2867 system-wide profiling i.e. per-process or workload profiling,
2868 but the version in danny doesn't yet take advantage of those 2868 but the version in danny doesn't yet take advantage of those
2869 capabilities (sysprof officially added the ability. 2869 capabilities (sysprof officially added the ability.
2870 to make use of perf_events just as we were going to press). 2870 to make use of perf_events just as we were going to press).
2871 </note> 2871 </informalexample>
2872 </section> 2872 </section>
2873 2873
2874 <section id='sysprof-documentation'> 2874 <section id='sysprof-documentation'>