These operations are made for installing the LTTng 0.86 tracer on a linux 2.6.X kernel. You will also find instructions for installation of LTTV 0.12.x : the @@ -66,7 +66,7 @@ the LTTng traces and the LTTV analysis tool.
ltt-armall
lttv-gui (or /usr/local/bin/lttv-gui) - Spot the "Tracing Control" icon : click on it @@ -384,7 +376,7 @@ Stop tracing and destroy trace channels : lttctl -D trace1 see lttctl --help for details. -+(note : to see if the buffers has been filled, look at the dmesg output after lttctl -R or after stopping tracing from the GUI, it will show an event lost @@ -398,14 +390,11 @@ Feel free to look in /usr/local/lib/lttv/plugins to see all the text and graphical plugins available.
For example, a simple trace dump in text format is available with : -
lttv -m textDump -t /tmp/trace-See lttv -m textDump --help for detailed command line options of textDump. -
It is, in the current state of the project, very useful to use "grep" on the text output to filter by specific event fields. You can later copy the timestamp @@ -414,18 +403,15 @@ bottom right label "Current time". Support for this type of filtering should be added to the filter module soon.
Starting from LTTng 0.5.105 and ltt-control 0.20, a new mode can be used : hybrid. It can be especially useful when studying big workloads on a long period of time. -
When using this mode, the most important, low rate control information will be recorded during all the trace by lttd (i.e. process creation/exit). The high rate information (i.e. interrupt/traps/syscall entry/exit) will be kept in a flight recorder buffer (now named flight-channelname_X). -
The following lttctl commands take an hybrid trace :
@@ -442,57 +428,73 @@ lttctl -D -w /tmp/trace2 trace2 Each "overwrite" channel is flight recorder channel.
The flight recorder mode writes data into overwritten buffers for all channels, including control channels, except for the facilities tracefiles. It consists of setting all channels to "overwrite". -
The following lttctl commands take a flight recorder trace : -
lttctl -C -w /tmp/trace3 -o channel.all.overwrite=1 trace3 ... lttctl -D -w /tmp/trace3 trace3-************************************************************** -** Section 4 * Adding new instrumentations with the markers ** -************************************************************** +
+
See Documentation/markers.txt and Documentation/tracepoints.txt in your kernel tree. -* Add new events to userspace programs with userspace markers -http://ltt.polymtl.ca/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. -*********************************************************** -** Section 5 * Creating Debian or RPM packages ** -*********************************************************** +See markers-userspace-0.5.tar.bz2 or more recent. -* Create custom LTTV Debian packages +Note that a new design document for a 3rd generation of tracepoint/marker-based +userspace tracing is available at LTTng User-space Tracing +Design". -Use : dpkg-buildpackage -rfakeroot +
-* Create custom LTTng packages +
+Use : dpkg-buildpackage -rfakeroot ++
+You should then have your LTTV .deb files created for your architecture. -Get the build tree with patches applies as explained in section 2. +
+For building LTTng Debian packages : +get the build tree with patches applies as explained in section 2. +
make menuconfig (or xconfig or config) (customize your configuration) make-kpkg kernel_image - ++
You will then see your freshly created .deb in /usr/src. Install it with +
dpkg -i /usr/src/(image-name).deb - ++
Then, follow the section "Editing the system wide configuration" in section 2.