|author||Scott Rifenbark <email@example.com>||2014-11-07 10:25:15 -0600|
|committer||Richard Purdie <firstname.lastname@example.org>||2014-11-08 11:14:57 +0000|
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: c56dab059b6edc02ffa2406b8e51c591e20fbe65) Signed-off-by: Scott Rifenbark <email@example.com> Signed-off-by: Richard Purdie <firstname.lastname@example.org>
1 files changed, 17 insertions, 7 deletions
diff --git a/documentation/profile-manual/profile-manual-usage.xml b/documentation/profile-manual/profile-manual-usage.xml
index 5279730a5b..1e4897e049 100644
@@ -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 @@
- <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.
@@ -3258,15 +3258,25 @@
- 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:
+ You can find the primary LTTng Documentation on the
+ <ulink url='https://lttng.org/docs/'>LTTng Documentation</ulink>
+ 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.
+ For information on LTTng in general, visit the
<ulink url='http://lttng.org/lttng2.0'>LTTng Project</ulink>
+ You can find a "Getting Started" link on this site that takes
+ you to an LTTng Quick Start.
- You can access extensive help information on how to use the
- LTTng plug-in to search and analyze captured traces via the
+ 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:
Help | Help Contents | LTTng Plug-in User Guide