X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=LTTngManual.html;h=10978001793975f4867738ff5f0bf34a4bcfa3dd;hb=0fe54b017fd76e78304066575103681ea7a36457;hp=58c49470a4bbfe3a3770a08a9e4c9c88d084a807;hpb=81654ff75bb53ee734f97e6307c54074f23c0e17;p=lttv.git diff --git a/LTTngManual.html b/LTTngManual.html index 58c49470..10978001 100644 --- a/LTTngManual.html +++ b/LTTngManual.html @@ -8,7 +8,7 @@
+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 +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 +licenses. +
+Please refer to each particular file licensing for details. +
See the list of compatibilities between LTTng, ltt-control and LTTV at : LTTng+LTTV -versions compatibility. +href="http://lttng.org/cgi-bin/gitweb.cgi?p=lttv.git;a=blob_plain;f=doc/developer/lttng-lttv-compatibility.html;hb=HEAD">LTTng+LTTV versions compatibility.
+su - +cd /usr/src/lttng/lttng-modules-0.x +KERNELDIR=/usr/src/linux-2.6.X-lttng-0.x.xx make +KERNELDIR=/usr/src/linux-2.6.X-lttng-0.x.xx make modules_install + +Optionally, make can be prefixed with tracer options: + +EXTRA_CFLAGS="-DLTT_DEBUG_EVENT_SIZE" make +EXTRA_CFLAGS="-DLTT_VMCORE" make +EXTRA_CFLAGS="-DLTT_DEBUG_EVENT_SIZE -DLTT_VMCORE" make ++
su - cd /usr/src -wget http://ltt.polymtl.ca/lttng/ltt-control-0.x-xxxx2006.tar.gz +wget http://lttng.org/files/lttng/ltt-control-0.x-xxxx2006.tar.gz gzip -cd ltt-control-0.x-xxxx2008.tar.gz | tar xvof - cd ltt-control-0.x-xxxx2006 (refer to README to see the development libraries that must be installed on you @@ -365,12 +388,12 @@ ldconfigMake 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 @@ -384,7 +407,7 @@ or different from the visualisation machine) su - cd /usr/src -wget http://ltt.polymtl.ca/packages/lttv-0.x.xx-xxxx2008.tar.gz +wget http://lttng.org/files/packages/lttv-0.x.xx-xxxx2008.tar.gz gzip -cd lttv-0.x.xx-xxxx2008.tar.gz | tar xvof - cd lttv-0.x.xx-xxxx2008 (refer to README to see the development libraries that must be installed on your @@ -523,18 +546,16 @@ for LTTng probe examples.Adding userspace instrumentation
Add new events to userspace programs with -userspace markers packages. +userspace markers packages. Get the latest markers-userspace-*.tar.bz2 and see the Makefile and examples. It allows inserting markers in executables and libraries, currently only on x86_32 and x86_64. See markers-userspace-0.5.tar.bz2 or more recent. +href="http://lttng.org/files/packages/markers-userspace-0.5.tar.bz2">markers-userspace-0.5.tar.bz2 or more recent.-Note that a new design document for a 3rd generation of tracepoint/marker-based -userspace tracing is available at LTTng User-space Tracing -Design. This new infrastructure is not yet implemented. +Note that tracepoint/marker-based userspace tracing is available at LTTng User-space Tracer (UST).
The easy quick-and-dirty way to perform userspace tracing is currently to write