sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

profile-manual: Updates to the LTTng Documentation section. 

The LTTng Documentation website has been updated to actually
have extensive documentation now.  Previously, in the profile-manual,
we were stating that documentation did not exist, which was true
at the time of writing.  I updated the section to link to the
main LTTng documentation website and altered some other text in
the section appropriately.

Additionally, I found and corrected a couple spelling errors in
this chapter.

(From yocto-docs rev: 6e03bd6b90726904a1ac54b8f16f6554b4bb22b8)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-11-07 10:25:15 -06:00 committed by Richard Purdie
parent 0d3e6853a6
commit 45bb9e3323
1 changed files with 18 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
documentation/profile-manual/profile-manual-usage.xml
View File

@ -842,7 +842,7 @@
idea. One of the first projects to do this was IBM's DProbes
dpcc compiler, an ANSI C compiler which targeted a low-level
assembly language running on an in-kernel interpreter on the
target system. This is exactly analagous to what Sun's DTrace
target system. This is exactly analogous to what Sun's DTrace
did, except that DTrace invented its own language for the purpose.
Systemtap, heavily inspired by DTrace, also created its own
one-off language, but rather than running the product on an
@ -1275,7 +1275,7 @@
</para>
<informalexample>
<emphasis>Tying it Together:</emphasis> The trace events subsystem accomodate static
<emphasis>Tying it Together:</emphasis> The trace events subsystem accommodate static
and dynamic tracepoints in exactly the same way - there's no
difference as far as the infrastructure is concerned. See the
ftrace section for more details on the trace event subsystem.
@ -3257,15 +3257,25 @@
<title>Documentation</title>
<para>
There doesn't seem to be any current documentation covering
LTTng 2.0, but maybe that's because the project is in transition.
The LTTng 2.0 website, however, is here:
<ulink url='http://lttng.org/lttng2.0'>LTTng Project</ulink>
You can find the primary LTTng Documentation on the
<ulink url='https://lttng.org/docs/'>LTTng Documentation</ulink>
site.
The documentation on this site is appropriate for intermediate to
advanced software developers who are working in a Linux environment
and are interested in efficient software tracing.
</para>
<para>
You can access extensive help information on how to use the
LTTng plug-in to search and analyze captured traces via the
For information on LTTng in general, visit the
<ulink url='http://lttng.org/lttng2.0'>LTTng Project</ulink>
site.
You can find a "Getting Started" link on this site that takes
you to an LTTng Quick Start.
</para>
<para>
Finally, you can access extensive help information on how to use
the LTTng plug-in to search and analyze captured traces via the
Eclipse help system:
<literallayout class='monospaced'>
Help | Help Contents | LTTng Plug-in User Guide