diff options
Diffstat (limited to 'documentation/profile-manual')
-rw-r--r-- | documentation/profile-manual/profile-manual-usage.xml | 24 |
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 d39126edd6..95ad73909c 100644 --- a/documentation/profile-manual/profile-manual-usage.xml +++ b/documentation/profile-manual/profile-manual-usage.xml | |||
@@ -842,7 +842,7 @@ | |||
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 |
844 | assembly language running on an in-kernel interpreter on the | 844 | assembly language running on an in-kernel interpreter on the |
845 | target system. This is exactly analagous to what Sun's DTrace | 845 | target system. This is exactly analogous to what Sun's DTrace |
846 | did, except that DTrace invented its own language for the purpose. | 846 | did, except that DTrace invented its own language for the purpose. |
847 | Systemtap, heavily inspired by DTrace, also created its own | 847 | Systemtap, heavily inspired by DTrace, also created its own |
848 | one-off language, but rather than running the product on an | 848 | one-off language, but rather than running the product on an |
@@ -1275,7 +1275,7 @@ | |||
1275 | </para> | 1275 | </para> |
1276 | 1276 | ||
1277 | <informalexample> | 1277 | <informalexample> |
1278 | <emphasis>Tying it Together:</emphasis> The trace events subsystem accomodate static | 1278 | <emphasis>Tying it Together:</emphasis> The trace events subsystem accommodate 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. |
@@ -3257,15 +3257,25 @@ | |||
3257 | <title>Documentation</title> | 3257 | <title>Documentation</title> |
3258 | 3258 | ||
3259 | <para> | 3259 | <para> |
3260 | There doesn't seem to be any current documentation covering | 3260 | You can find the primary LTTng Documentation on the |
3261 | LTTng 2.0, but maybe that's because the project is in transition. | 3261 | <ulink url='https://lttng.org/docs/'>LTTng Documentation</ulink> |
3262 | The LTTng 2.0 website, however, is here: | 3262 | site. |
3263 | The documentation on this site is appropriate for intermediate to | ||
3264 | advanced software developers who are working in a Linux environment | ||
3265 | and are interested in efficient software tracing. | ||
3266 | </para> | ||
3267 | |||
3268 | <para> | ||
3269 | For information on LTTng in general, visit the | ||
3263 | <ulink url='http://lttng.org/lttng2.0'>LTTng Project</ulink> | 3270 | <ulink url='http://lttng.org/lttng2.0'>LTTng Project</ulink> |
3271 | site. | ||
3272 | You can find a "Getting Started" link on this site that takes | ||
3273 | you to an LTTng Quick Start. | ||
3264 | </para> | 3274 | </para> |
3265 | 3275 | ||
3266 | <para> | 3276 | <para> |
3267 | You can access extensive help information on how to use the | 3277 | Finally, you can access extensive help information on how to use |
3268 | LTTng plug-in to search and analyze captured traces via the | 3278 | the LTTng plug-in to search and analyze captured traces via the |
3269 | Eclipse help system: | 3279 | Eclipse help system: |
3270 | <literallayout class='monospaced'> | 3280 | <literallayout class='monospaced'> |
3271 | Help | Help Contents | LTTng Plug-in User Guide | 3281 | Help | Help Contents | LTTng Plug-in User Guide |