X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=LTTngManual.html;h=020a7270d1bc59286bc20aa57b26fbb6505dce2a;hb=cf1edabde5ccde390704f76d7a1bf9edfd964660;hp=b46ae9a11590c161c23dac09a1964b34f145aac6;hpb=2eec045bcb4aeb474c751934be8ac1829c4be330;p=lttv.git diff --git a/LTTngManual.html b/LTTngManual.html index b46ae9a1..020a7270 100644 --- a/LTTngManual.html +++ b/LTTngManual.html @@ -8,7 +8,7 @@

Linux Trace Toolkit Next Generation Manual

Author : Mathieu Desnoyers, September 2005
-Last update : January 21st, 2009
+Last update : January 30, 2010
(originally known as the LTTng QUICKSTART guide)

Table of Contents

@@ -90,7 +90,6 @@ kernel.

Licenses

-

LTTng, UST and LTTV are developed by an open community. LTTng is released under a dual Gnu LGPLv2.1/GPLv2 license, except for very few kernel-specific files @@ -99,6 +98,9 @@ which are derived work from the Linux kernel. LTTV is available under the Gnu GPLv2. The low-level LTTV trace reading library is released under Gnu LGPLv2.1.

+The Eclipse LTTng trace analysis tool is released under the EPL and uses the +LTTV trace reading library (LGPLv2.1). +

The UST (Userspace Tracing) and the Userspace RCU libraries are released under the LGPLv2.1 license, which allows linking with non-GPL (BSD, proprietary...) applications. The associated headers are released under MIT-style/BSD-style @@ -106,10 +108,7 @@ licenses.

Please refer to each particular file licensing for details. -
-

Supported architectures

-
LTTng :

  • x86 32/64 bits @@ -175,7 +174,7 @@ gtk 2.4 or better development libraries (Fedora : gtk2, gtk2-devel) note : For Fedora users : this might require at least core 3 from Fedora, or you might have to compile your own GTK2 library. -glib 2.4 or better development libraries +glib 2.16 or better development libraries (Debian : libglib2.0-0, libglib2.0-dev) (Fedora : glib2, glib2-devel) libpopt development libraries @@ -233,7 +232,7 @@ mv linux-2.6.X linux-2.6.X-lttng-0.x.xx su - cd /usr/src/linux-2.6.X-lttng-0.x.xx make menuconfig (or make xconfig or make config) - Select the < Help > button if you are not familiar with kernel + Select the < Help > button if you are not familiar with kernel configuration. Items preceded by [*] means they has to be built into the kernel. Items preceded by [M] means they has to be built as modules. @@ -244,21 +243,21 @@ make menuconfig (or make xconfig or make config) [*] Activate markers [*] Activate userspace markers ABI (experimental, optional) [*] Immediate value optimization (optional) - [*] Linux Trace Toolkit Next Generation (LTTng) ---> - or <*> Compile lttng tracing probes - or <*> Linux Trace Toolkit High-speed Lockless Data Relay - or <*> Linux Trace Toolkit Lock-Protected Data Relay - or <*> Linux Trace Toolkit Serializer - or <*> Linux Trace Toolkit Marker Control - or <*> Linux Trace Toolkit Tracer + [*] Linux Trace Toolkit Next Generation (LTTng) ---> + <M> or <*> Compile lttng tracing probes + <M> or <*> Linux Trace Toolkit High-speed Lockless Data Relay + <M> or <*> Linux Trace Toolkit Lock-Protected Data Relay + <M> or <*> Linux Trace Toolkit Serializer + <M> or <*> Linux Trace Toolkit Marker Control + <M> or <*> Linux Trace Toolkit Tracer [*] Align Linux Trace Toolkit Traces - or <*> Support logging events from userspace + <M> or <*> Support logging events from userspace [*] Support trace extraction from crash dump - or <*> Linux Trace Toolkit Trace Controller - or <*> Linux Trace Toolkit State Dump - Select - Select - Select + <M> or <*> Linux Trace Toolkit Trace Controller + <M> or <*> Linux Trace Toolkit State Dump + Select <Exit> + Select <Exit> + Select <Yes> make make modules_install (if necessary, create a initrd with mkinitrd or your preferate alternative) @@ -386,12 +385,12 @@ ldconfig
     Make sure you selected the kernel menuconfig option :
    -     or <*> Support logging events from userspace
    +    <M> or <*> Support logging events from userspace
     And that the ltt-userspace-event kernel module is loaded if selected as a
     module.
     
     Simple userspace tracing is available through
    -echo "some text to record" > /mnt/debugfs/ltt/write_event
    +echo "some text to record" > /mnt/debugfs/ltt/write_event
     
     It will appear in the trace under event :
     channel : userspace