update ltt control
[lttv.git] / ltt / branches / poly / QUICKSTART
... / ...
CommitLineData
1
2QUICKSTART
3
4How to use LTTng and LTTV in a few lines :
5
6This document is made of four parts : The first one explains how to install
7LTTng and LTTV from Debian and RPM binary packages, the second one explains how
8to install LTTng and LTTV from sources and the third one describes the steps
9to follow to trace a system and view it. The fourth and last part explains
10briefly how to add a new trace point to the kernel and to user space
11applications.
12
13What you will typically want is to read sections 2 and 3 : install LTTng from
14sources and use it.
15
16These operations are made for installing the LTTng 0.5.X tracer on a
17linux 2.6.X kernel. You will also find instructions for installation of
18LTTV 0.8.x : the Linux Trace Toolkit Viewer.
19
20To see the list of compatibilities between LTTng, ltt-control, LTTV, genevent
21and ltt-usertrace, please refer to :
22http://ltt.polymtl.ca > LTTng+LTTV versions compatibility
23
24
25
26The following lttng patch is necessary to have the tracing hooks in the kernel.
27The following ltt-control module controls the tracing.
28
29Required programs and librairies are assumed to be automatically installed in an
30installation with Debian or RPM packages. In the case of an installation from
31sources, the dependencies are listed.
32
33
34** Current development status **
35
36LTTng :
37supported architectures :
38Intel Pentium (UP/SMP) with TSC
39PowerPC 32 and 64 bits
40ARM
41x86_64
42C2 Microsystems (variant of MIPS)
43
44LTTV :
45supported architectures :
46Intel i386 and better
47Intel 64 bits
48PowerPC 32 and 64 bits
49
50
51
52Author : Mathieu Desnoyers, September 2005
53Last update : May 30, 2006
54
55
56***********************************************************
57** Section 1 * Installation from Debian or RPM packages **
58***********************************************************
59
60** NOTE : RPM and debian packages are only made once a version has been
61 thoroughly tested. If they do not exist at the moment, please install from
62 sources (see section 2 below). To see the list of compatibilities between
63 LTTng, ltt-control, LTTV, genevent and lttng-modules, please refer to
64 http://ltt.polymtl.ca > LTTng+LTTV versions compatibility
65
66
67* Install from RPM packages on Fedora Core 4 :
68
69Get LTTV RPM from :
70
71http://ltt.polymtl.ca/packages/fedora/RPMS
72
73LTTV RPM are ready.
74
75LTTng kernel and lttng-modules RPM are available for some architectures (i586,
76i686). Feel free to help fix the spec files to have correct lttng-modules RPM
77package.
78
79
80* Install from Deb packages on Debian :
81
82You can use the ltt.polymtl.ca apt source to get LTTV for Debian :
83
84Add the following two sources to your /etc/apt/sources.list :
85
86deb http://ltt.polymtl.ca/packages/debian experimental main
87deb-src http://ltt.polymtl.ca/packages/debian experimental main
88
89
90* Install from precompiled binary packages (LTTV compiled only for i386, and
91 LTTng only for i686 smp), perform the following :
92
93su -
94apt-get update
95apt-get install lttv lttv-doc
96apt-get install kernel-image-2.6.12-rc4-mm2-lttng-0.4.2
97apt-get install lttng-modules-modules-2.6.12-rc4-mm2-lttng-0.4.2
98 * note : the packages are signed by myself. I am not considered a trusted
99 Debian source yet, so warnings are normal.
100
101Then, follow the section "Editing the system wide configuration" in section 2.
102
103* Create custom LTTV Debian packages
104
105Binary packages are only available for i386. If you want to create your own LTTV
106packages for other platforms, do :
107
108su -
109cd /usr/src
110apt-get source lttv
111cd lttv-0.6.9
112dpkg-buildpackage -rfakeroot
113
114You should then have your LTTV .deb files created for your architecture.
115
116* Create custom LTTng packages
117
118For building LTTng Debian packages :
119
120su -
121apt-get install kernel-source-2.6.12-rc4-mm2-lttng-0.4.2
122cd /usr/src
123bzip2 -cd kernel-source-2.6.12-rc4-mm2-lttng-0.4.2.tar.bz2 | tar xvof -
124cd kernel-source-2.6.12-rc4-mm2-lttng-0.4.2
125make menuconfig (or xconfig or config) (customize your configuration)
126make-kpkg kernel_image
127
128You will then see your freshly created .deb in /usr/src. Install it with
129dpkg -i /usr/src/(image-name).deb
130
131You will also need to create a package for the lttng-modules :
132
133su -
134cd /usr/src
135apt-get source lttng-modules
136cd kernel-source-2.6.12-rc4-mm2-lttng-0.4.2
137make-kpkg --added_modules /usr/src/lttng-modules-0.3 modules_image
138
139You will then see your freshly created .deb in /usr/src. Install it with
140dpkg -i /usr/src/lttng-modules-modules-(your version).deb
141
142
143Then, follow the section "Editing the system wide configuration" in section 2.
144
145
146***********************************************************
147** Section 2 * Installation from sources **
148***********************************************************
149
150* Prerequisites
151
152Tools needed to follow the package download steps :
153
154o wget
155o bzip2
156o gzip
157o tar
158
159You have to install the standard development librairies and programs necessary
160to compile a kernel :
161
162(from Documentation/Changes in the Linux kernel tree)
163o Gnu C 2.95.3 # gcc --version
164o Gnu make 3.79.1 # make --version
165o binutils 2.12 # ld -v
166o util-linux 2.10o # fdformat --version
167o module-init-tools 0.9.10 # depmod -V
168
169You might also want to have libncurses5 to have the text mode kernel
170configuration menu, but there are alternatives.
171
172Prerequisites for LTTV 0.x.x installation are :
173
174gcc 3.2 or better
175gtk 2.4 or better development libraries
176 (Debian : libgtk2.0, libgtk2.0-dev)
177 (Fedora : gtk2, gtk2-devel)
178 note : For Fedora users : this might require at least core 3 from Fedora,
179 or you might have to compile your own GTK2 library.
180glib 2.4 or better development libraries
181 (Debian : libglib2.0-0, libglib2.0-dev)
182 (Fedora : glib2, glib2-devel)
183libpopt development libraries
184 (Debian : libpopt0, libpopt-dev)
185 (Fedora : popt)
186libpango development libraries
187 (Debian : libpango1.0, libpango1.0-dev)
188 (Fedora : pango, pango-devel)
189libc6 development librairies
190 (Debian : libc6, libc6-dev)
191 (Fedora : glibc, glibc)
192
193
194* Getting the LTTng packages
195
196su -
197mkdir /usr/src/lttng
198cd /usr/src/lttng
199(see http://ltt.polymtl.ca/lttng for package listing)
200wget http://ltt.polymtl.ca/lttng/patch-2.6.X-lttng-0.x.xx.tar.bz2
201bzip2 -cd patch-2.6.X-lttng-0.x.xx.tar.bz2 | tar xvof -
202
203
204* Getting LTTng kernel sources
205
206su -
207cd /usr/src
208wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.X.tar.bz2
209bzip2 -cd linux-2.6.X.tar.bz2 | tar xvof -
210cd linux-2.6.X
211cat /usr/src/lttng/patch-2.6.X-lttng-0.x.xx* | patch -p1
212cd ..
213mv linux-2.6.X linux-2.6.X-lttng-0.x.xx
214
215
216* Installing a LTTng kernel
217
218su -
219cd /usr/src/linux-2.6.X-lttng-0.x.xx
220make menuconfig (or make xconfig or make config)
221 Select the < Help > button if you are not familiar with kernel
222 configuration.
223 Items preceded by [*] means they has to be built into the kernel.
224 Items preceded by [M] means they has to be built as modules.
225 Items preceded by [ ] means they should be removed.
226 go to the "Instrumentation Support" section
227 Select the following options :
228 [*] Linux Trace Toolkit Instrumentation Support
229 <M> or <*> Linux Trace Toolkit Tracer
230 It makes no difference for the rest of the procedure whether the Tracer
231 is compiled built-in or as a module.
232 activate :
233 [*] Align Linux Trace Toolkit Traces
234 [*] Allow tracing from userspace
235 your choice (see < Help >) :
236 [ ] Activate Linux Trace Toolkit Heartbeat Timer
237 You may or may not activate instrumentation per facility. They are all
238 selected for logging by default. It can be used as a compile time filter to
239 enable/disable logging of events. It is useful to discard events with a
240 minimal impact on the system and especially useful for now, as the dynamic
241 filter has not been implemented yet.
242 Select <Exit>
243 Select <Exit>
244 Select <Yes>
245make
246make modules_install
247
248-- on X86, X86_64
249make install
250reboot
251Select the Linux 2.6.17-lttng-0.x.xx kernel in your boot loader.
252
253-- on PowerPC
254cp vmlinux.strip /boot/vmlinux-2.6.X-lttng-0.x.xx
255cp System.map /boot/System.map-2.6.X-lttng-0.x.xx
256cp .config /boot/config-2.6.X-lttng-0.x.xx
257depmod -ae -F /boot/System.map-2.6.X-lttng-0.x.xx 2.6.X-lttng-0.x.xx
258mkinitrd /boot/initrd.img-2.6.X-lttng-0.x.xx 2.6.X-lttng-0.x.xx
259(edit /etc/yaboot.conf to add a new entry pointing to your kernel : the entry
260that comes first is the default kernel)
261ybin
262select the right entry at the yaboot prompt (see choices : tab, select : type
263the kernel name followed by enter)
264Select the Linux 2.6.17-lttng-0.x.xx kernel in your boot loader.
265--
266
267
268
269* Editing the system wide configuration
270
271You must activate relayfs and specify a mount point. This is typically done in
272fstab such that it happens at boot time.
273
274If you have never used RelayFS before, these operation would do this for you :
275
276mkdir /mnt/relayfs
277cp /etc/fstab /etc/fstab.lttng.bkp
278echo "relayfs /mnt/relayfs relayfs rw 0 0" >> /etc/fstab
279
280then, rebooting or issuing the following command will activate relayfs :
281
282mount /mnt/relayfs
283
284You need to load the ltt-control module to be able to control tracing from user
285space. This is done by issuing the command :
286
287modprobe ltt-control
288
289If you want to have complete information about the kernel state (including all
290the process names), you need to load the ltt-statedump module. This is done by
291issuing the command :
292
293modprobe ltt-statedump
294
295You can automate at boot time loading the ltt-control module by :
296
297echo ltt-control >> /etc/modules
298echo ltt-statedump >> /etc/modules
299
300
301* Getting and installing the ltt-control package (on the traced machine)
302(note : the ltt-control package contains lttd and lttctl. Although it has the
303same name as the ltt-control kernel module, they are *not* the same thing.)
304su -
305cd /usr/src
306wget http://ltt.polymtl.ca/lttng/ltt-control-0.x-xxxx2006.tar.gz
307gzip -cd ltt-control-0.x-xxxx2006.tar.gz | tar xvof -
308cd ltt-control-0.x-xxxx2006
309(refer to README to see the development libraries that must be installed on you
310system)
311./configure
312make
313make install
314
315* Getting and installing the ltt-usertrace package for user space tracing
316See http://ltt.polymtl.ca/ > USERSPACE TRACING QUICKSTART
317
318
319* Getting and installing the LTTV package (on the visualisation machine, same or
320 different from the visualisation machine)
321
322su -
323cd /usr/src
324wget http://ltt.polymtl.ca/packages/LinuxTraceToolkitViewer-0.x.xx-xxxx2006.tar.gz
325gzip -cd LinuxTraceToolkitViewer-0.x.xx-xxxx2006.tar.gz | tar xvof -
326cd LinuxTraceToolkitViewer-0.x.xx-xxxx2006
327(refer to README to see the development libraries that must be installed on you
328system)
329./configure
330make
331make install
332
333
334
335
336***********************************************************
337** Section 3 * Using LTTng and LTTV **
338***********************************************************
339
340* Use graphical LTTV to control tracing and analyse traces
341
342lttv-gui (or /usr/local/bin/lttv-gui)
343 - Spot the "Tracing Control" icon : click on it
344 (it's a traffic light icon)
345 - enter the root password
346 - click "start"
347 - click "stop"
348 - Yes
349 * You should now see a trace
350
351* Use text mode LTTng to control tracing
352
353The tracing can be controlled from a terminal by using the lttctl command (as
354root).
355
356Start tracing :
357
358lttctl -n trace -d -l /mnt/relayfs/ltt -t /tmp/trace
359
360Stop tracing and destroy trace channels :
361
362lttctl -n trace -R
363
364see lttctl --help for details.
365
366
367* Use text mode LTTV
368
369Fell free to look in /usr/local/lib/lttv/plugins to see all the text and
370graphical plugins available.
371
372For example, a simple trace dump in text format is available with :
373
374lttv -m textDump -t /tmp/trace
375
376see lttv -m textDump --help for detailed command line options of textDump.
377
378
379
380
381***********************************************************
382** Section 4 * Adding new instrumentations with genevent **
383***********************************************************
384
385* Getting and installing genevent
386
387su -
388cd /usr/src
389wget http://ltt.polymtl.ca/packages/genevent-0.xx.tar.gz
390gzip -cd genevent-0.xx.tar.gz | tar xvof -
391cd genevent-0.xx
392make
393make install
394
395
396* Add new events to the kernel with genevent
397
398su -
399cd /usr/local/share/LinuxTraceToolkitViewer/facilities
400cp process.xml yourfacility.xml
401 * edit yourfacility.xml to fit your needs.
402cd /tmp
403/usr/local/bin/genevent /usr/local/share/LinuxTraceToolkitViewer/facilities/yourfacility.xml
404cp ltt-facility-yourfacility.h ltt-facility-id-yourfacility.h \
405 /usr/src/linux-2.6.17-lttng-0.x.xx8/include/linux/ltt
406cp ltt-facility-loader-yourfacility.c ltt-facility-loader-yourfacility.h \
407 /usr/src/linux-2.6.17-lttng-0.x.xx/ltt
408 * edit the kernel file you want to instrument
409 - Add #include <linux/ltt/ltt-facility-yourfacility.h> at the beginning
410 of the file.
411 - Add a call to the tracing functions. See their names and parameters in
412 /usr/src/linux-2.6.17-lttng-0.x.xx/include/linux/ltt/ltt-facility-yourfacility.h
413
414* Add new events to userspace programs with genevent
415See http://ltt.polymtl.ca/ > USERSPACE TRACING QUICKSTART
416
417
418
419
This page took 0.023092 seconds and 4 git commands to generate.