c924c2c6 |
1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
2 | <html> |
3 | <head> |
bc58079d |
4 | <title>Linux Trace Toolkit Next Generation User Documentation</title> |
c924c2c6 |
5 | </head> |
6 | <body> |
7 | |
bc58079d |
8 | <h1>Linux Trace Toolkit Next Generation User Documentation</h1> |
c924c2c6 |
9 | |
c924c2c6 |
10 | Author : Mathieu Desnoyers, September 2005<br> |
24070967 |
11 | Last update : January 21st, 2009<br> |
bc58079d |
12 | (originally known as the LTTng QUICKSTART guide) |
24070967 |
13 | |
14 | <h2>Table of Contents</h2> |
24070967 |
15 | |
d58b406f |
16 | <ul> |
f9ff56f3 |
17 | <li><a href="#intro" name="TOCintro">Introduction</a></li> |
7e77d1a9 |
18 | <ul> |
19 | <li><a href="#arch" name="TOCarch">Supported architectures</a></li> |
20 | </ul> |
d58b406f |
21 | |
24070967 |
22 | <li><a href="#section1" name="TOCsection1">Installing LTTng and LTTV from |
6f88b01d |
23 | sources</a></li> |
38b04cd7 |
24 | <ul> |
2d540155 |
25 | <li><a href="#prerequisites" name="TOCprerequisites">Prerequisistes</li> |
26 | <li><a href="#getlttng" name="TOCgetlttng">Getting the LTTng packages</li> |
27 | <li><a href="#getlttngsrc" name="TOCgetlttngsrc">Getting the LTTng kernel sources</li> |
28 | <li><a href="#installlttng" name="TOCinstalllttng">Installing a LTTng kernel</li> |
6f88b01d |
29 | <li><a href="#editconfig" name="TOCeditconfig">Editing the system wide |
30 | configuration</a> |
31 | <li><a href="#getlttctl" name="TOCgetlttctl">Getting and installing the |
2d540155 |
32 | ltt-control package</li> |
33 | <li><a href="#userspacetracing" name="TOCuserspacetracing">Userspace Tracing</li> |
6f88b01d |
34 | <li><a href="#getlttv" name="TOCgetlttv">Getting and installing the LTTV package</ul> |
d58b406f |
35 | |
24070967 |
36 | <li><a href="#section2" name="TOCsection2">Using LTTng and LTTV</a></li> |
d58b406f |
37 | <ul> |
38 | <li><a href="#uselttvgui" name="TOCuselttvgui">Use graphical LTTV to control |
39 | tracing and analyse traces</a></li> |
40 | <li><a href="#uselttngtext" name="TOCuselttngtext">Use text mode LTTng to |
f7828b7c |
41 | control tracing</a></li> |
d58b406f |
42 | <li><a href="#uselttvtext" name="TOCuselttvtext">Use text mode LTTV</a></li> |
43 | <li><a href="#hybrid" name="TOChybrid">Tracing in "Hybrid" mode</a></li> |
44 | <li><a href="#flight" name="TOCflight">Tracing in flight recorder mode</a></li> |
d58b406f |
45 | </ul> |
46 | |
24070967 |
47 | <li><a href="#section3" name="TOCsection3">Adding kernel and user-space |
47e2b195 |
48 | instrumentation</a> |
49 | <ul> |
50 | <li><a href="#kerneltp" name="TOCkerneltp">Adding kernel instrumentation</a></li> |
51 | <li><a href="#usertp" name="TOCusertp">Adding userspace instrumentation</a></li> |
52 | </ul> |
d58b406f |
53 | |
633bc4a3 |
54 | <li><a href="#section4" name="TOCsection4">Creating Debian and RPM packages |
98dde887 |
55 | from LTTV</a></li> |
56 | <ul> |
57 | <li><a href="#pkgdebian" name="TOCpkgdebian">Create custom LTTV Debian |
58 | <li><a href="#pkglttng" name="TOCpkglttng">Create custom LTTng packages</a></li> |
98dde887 |
59 | </ul> |
c924c2c6 |
60 | |
70a3fc43 |
61 | <li><a href="#section5" name="TOCsection5">Examples of LTTng use in the |
62 | field</a></li> |
63 | |
f9ff56f3 |
64 | </ul> |
65 | |
66 | <hr /> |
67 | |
b9e1fab1 |
68 | <h2><a href="#TOCintro" name="intro">Introduction</a></h2> |
c924c2c6 |
69 | <p> |
70a3fc43 |
70 | This document is made of five parts : the first one explains how |
24070967 |
71 | to install LTTng and LTTV from sources, the second one describes the steps |
633bc4a3 |
72 | to follow to trace a system and view it. The third part explains |
c924c2c6 |
73 | briefly how to add a new trace point to the kernel and to user space |
70a3fc43 |
74 | applications. The fourth part explains how to create Debian or RPM |
75 | packages from the LTTng and LTTV sources. The fifth and last part describes use |
76 | of LTTng in the field. |
c924c2c6 |
77 | <p> |
24070967 |
78 | These operations are made for installing the LTTng 0.86 tracer on a linux 2.6.X |
c924c2c6 |
79 | kernel. You will also find instructions for installation of LTTV 0.12.x : the |
80 | Linux Trace Toolkit Viewer. |
24070967 |
81 | To see the list of compatibilities between LTTng, ltt-control, LTTV, please |
82 | refer to : |
c924c2c6 |
83 | <a |
84 | href="http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/lttng-lttv-compatibility.html">LTTng+LTTV versions compatibility</a> |
24070967 |
85 | The lttng patch is necessary to have the tracing hooks in the kernel. |
c924c2c6 |
86 | |
24070967 |
87 | <br> |
88 | <br> |
7e77d1a9 |
89 | <h3><a href="#TOCarch" name="arch">Supported architectures</a></h3> |
70a3fc43 |
90 | <br> |
c924c2c6 |
91 | LTTng :<br> |
70a3fc43 |
92 | <br> |
c924c2c6 |
93 | <li> x86 32/64 bits |
94 | <li> PowerPC 32 and 64 bits |
95 | <li> ARM (with limited timestamping precision, e.g. 1HZ. Need |
96 | architecture-specific support for better precision) |
97 | <li> MIPS |
1aeeacdb |
98 | <li> sh (partial architecture-specific instrumentation) |
99 | <li> sparc64 (partial architecture-specific instrumentation) |
100 | <li> s390 (partial architecture-specific instrumentation) |
101 | <li> Other architectures supported without architecture-specific instrumentation |
102 | and with low-resolution timestamps.<br> |
c924c2c6 |
103 | <br> |
24070967 |
104 | <br> |
c924c2c6 |
105 | LTTV :<br> |
70a3fc43 |
106 | <br> |
c924c2c6 |
107 | <li> Intel 32/64 bits |
108 | <li> PowerPC 32 and 64 bits |
109 | <li> Possibly others. Takes care of endianness and type size difference between |
110 | the LTTng traces and the LTTV analysis tool. |
111 | |
f9ff56f3 |
112 | <hr /> |
113 | |
c924c2c6 |
114 | |
89aa576c |
115 | <h2><a href="#TOCsection1" name="section1">Installation from sources</a></h2> |
633bc4a3 |
116 | <p> |
c924c2c6 |
117 | |
6f88b01d |
118 | <h3><a href="#TOCprerequisites" name="prerequisites">Prerequisites</a></h3> |
633bc4a3 |
119 | <ul> |
120 | <p> |
c924c2c6 |
121 | Tools needed to follow the package download steps : |
122 | |
633bc4a3 |
123 | <li>wget |
124 | <li>bzip2 |
125 | <li>gzip |
126 | <li>tar |
c924c2c6 |
127 | |
633bc4a3 |
128 | <p> |
c924c2c6 |
129 | You have to install the standard development libraries and programs necessary |
130 | to compile a kernel : |
131 | |
84cf5903 |
132 | <PRE> |
c924c2c6 |
133 | (from Documentation/Changes in the Linux kernel tree) |
84cf5903 |
134 | Gnu C 2.95.3 # gcc --version |
135 | Gnu make 3.79.1 # make --version |
136 | binutils 2.12 # ld -v |
137 | util-linux 2.10o # fdformat --version |
138 | module-init-tools 0.9.10 # depmod -V |
139 | </PRE> |
c924c2c6 |
140 | |
633bc4a3 |
141 | <p> |
c924c2c6 |
142 | You might also want to have libncurses5 to have the text mode kernel |
143 | configuration menu, but there are alternatives. |
144 | |
633bc4a3 |
145 | <p> |
c924c2c6 |
146 | Prerequisites for LTTV 0.x.x installation are : |
147 | |
84cf5903 |
148 | <PRE> |
149 | gcc 3.2 or better |
150 | gtk 2.4 or better development libraries |
c924c2c6 |
151 | (Debian : libgtk2.0, libgtk2.0-dev) |
152 | (Fedora : gtk2, gtk2-devel) |
153 | note : For Fedora users : this might require at least core 3 from Fedora, |
154 | or you might have to compile your own GTK2 library. |
84cf5903 |
155 | glib 2.4 or better development libraries |
c924c2c6 |
156 | (Debian : libglib2.0-0, libglib2.0-dev) |
157 | (Fedora : glib2, glib2-devel) |
84cf5903 |
158 | libpopt development libraries |
c924c2c6 |
159 | (Debian : libpopt0, libpopt-dev) |
160 | (Fedora : popt) |
84cf5903 |
161 | libpango development libraries |
c924c2c6 |
162 | (Debian : libpango1.0, libpango1.0-dev) |
163 | (Fedora : pango, pango-devel) |
84cf5903 |
164 | libc6 development librairies |
c924c2c6 |
165 | (Debian : libc6, libc6-dev) |
166 | (Fedora : glibc, glibc) |
84cf5903 |
167 | </PRE> |
633bc4a3 |
168 | </ul> |
c924c2c6 |
169 | |
c8997124 |
170 | <li>Reminder</li> |
c924c2c6 |
171 | |
c8997124 |
172 | <p> |
633bc4a3 |
173 | See the list of compatibilities between LTTng, ltt-control and LTTV at : |
174 | <a |
175 | href="http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/lttng-lttv-compatibility.html">LTTng+LTTV |
176 | versions compatibility</a>. |
c924c2c6 |
177 | |
178 | |
6f88b01d |
179 | <h3><a href="#TOCgetlttng" name="getlttng">Getting the LTTng packages</a></h3> |
c924c2c6 |
180 | |
c8997124 |
181 | <PRE> |
c924c2c6 |
182 | su - |
183 | mkdir /usr/src/lttng |
184 | cd /usr/src/lttng |
185 | (see http://ltt.polymtl.ca/lttng for package listing) |
186 | wget http://ltt.polymtl.ca/lttng/patch-2.6.X-lttng-0.x.xx.tar.bz2 |
187 | bzip2 -cd patch-2.6.X-lttng-0.x.xx.tar.bz2 | tar xvof - |
c8997124 |
188 | </PRE> |
c924c2c6 |
189 | |
190 | |
6f88b01d |
191 | <h3><a href="#TOCgetlttngsrc" name="getlttngsrc">Getting LTTng kernel sources</a></h3> |
c924c2c6 |
192 | |
c8997124 |
193 | <PRE> |
c924c2c6 |
194 | su - |
195 | cd /usr/src |
196 | wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.X.tar.bz2 |
197 | bzip2 -cd linux-2.6.X.tar.bz2 | tar xvof - |
198 | cd linux-2.6.X |
199 | - For LTTng 0.9.4- cat /usr/src/lttng/patch*-2.6.X-lttng-0.x.xx* | patch -p1 |
200 | - For LTTng 0.9.5+ apply the patches in the order specified in the series file, |
201 | or use quilt |
202 | cd .. |
203 | mv linux-2.6.X linux-2.6.X-lttng-0.x.xx |
c8997124 |
204 | </PRE> |
c924c2c6 |
205 | |
206 | |
6f88b01d |
207 | <h3><a href="#TOCinstalllttng" name="installlttng">Installing a LTTng kernel</a></h3> |
c924c2c6 |
208 | |
c8997124 |
209 | <PRE> |
c924c2c6 |
210 | su - |
211 | cd /usr/src/linux-2.6.X-lttng-0.x.xx |
212 | make menuconfig (or make xconfig or make config) |
213 | Select the < Help > button if you are not familiar with kernel |
214 | configuration. |
215 | Items preceded by [*] means they has to be built into the kernel. |
216 | Items preceded by [M] means they has to be built as modules. |
217 | Items preceded by [ ] means they should be removed. |
218 | go to the "General setup" section |
219 | Select the following options : |
220 | [*] Prompt for development and/or incomplete code/drivers |
221 | [*] Activate markers |
222 | [*] Activate userspace markers ABI (experimental, optional) |
223 | [*] Immediate value optimization (optional) |
224 | [*] Linux Trace Toolkit Next Generation (LTTng) ---> |
225 | <M> or <*> Compile lttng tracing probes |
226 | <M> or <*> Linux Trace Toolkit High-speed Lockless Data Relay |
227 | <M> or <*> Linux Trace Toolkit Lock-Protected Data Relay |
228 | <M> or <*> Linux Trace Toolkit Serializer |
229 | <M> or <*> Linux Trace Toolkit Marker Control |
230 | <M> or <*> Linux Trace Toolkit Tracer |
231 | [*] Align Linux Trace Toolkit Traces |
232 | <M> or <*> Support logging events from userspace |
233 | [*] Support trace extraction from crash dump |
234 | <M> or <*> Linux Trace Toolkit Trace Controller |
235 | <M> or <*> Linux Trace Toolkit State Dump |
236 | Select <Exit> |
237 | Select <Exit> |
238 | Select <Yes> |
239 | make |
240 | make modules_install |
241 | (if necessary, create a initrd with mkinitrd or your preferate alternative) |
242 | (mkinitrd -o /boot/initrd.img-2.6.X-lttng-0.x.xx 2.6.X-lttng-0.x.xx) |
243 | |
244 | -- on X86, X86_64 |
245 | make install |
246 | reboot |
247 | Select the Linux 2.6.X-lttng-0.x.xx kernel in your boot loader. |
248 | |
249 | -- on PowerPC |
250 | cp vmlinux.strip /boot/vmlinux-2.6.X-lttng-0.x.xx |
251 | cp System.map /boot/System.map-2.6.X-lttng-0.x.xx |
252 | cp .config /boot/config-2.6.X-lttng-0.x.xx |
253 | depmod -ae -F /boot/System.map-2.6.X-lttng-0.x.xx 2.6.X-lttng-0.x.xx |
254 | mkinitrd /boot/initrd.img-2.6.X-lttng-0.x.xx 2.6.X-lttng-0.x.xx |
255 | (edit /etc/yaboot.conf to add a new entry pointing to your kernel : the entry |
256 | that comes first is the default kernel) |
257 | ybin |
258 | select the right entry at the yaboot prompt (see choices : tab, select : type |
259 | the kernel name followed by enter) |
260 | Select the Linux 2.6.X-lttng-0.x.xx kernel in your boot loader. |
261 | -- |
c8997124 |
262 | </PRE> |
c924c2c6 |
263 | |
6f88b01d |
264 | <h3><a href="#TOCeditconfig" name="editconfig">Editing the system wide |
265 | configuration</a></h3> |
c924c2c6 |
266 | |
c8997124 |
267 | <p> |
c924c2c6 |
268 | You must activate debugfs and specify a mount point. This is typically done in |
c8997124 |
269 | fstab such that it happens at boot time. If you have never used DebugFS before, |
270 | these operation would do this for you : |
c924c2c6 |
271 | |
c8997124 |
272 | <PRE> |
c924c2c6 |
273 | mkdir /mnt/debugfs |
274 | cp /etc/fstab /etc/fstab.lttng.bkp |
275 | echo "debugfs /mnt/debugfs debugfs rw 0 0" >> /etc/fstab |
c8997124 |
276 | </PRE> |
c924c2c6 |
277 | |
c8997124 |
278 | <p> |
c924c2c6 |
279 | then, rebooting or issuing the following command will activate debugfs : |
c8997124 |
280 | <PRE> |
c924c2c6 |
281 | mount /mnt/debugfs |
c8997124 |
282 | </PRE> |
c924c2c6 |
283 | |
c8997124 |
284 | <p> |
c924c2c6 |
285 | You need to load the LTT modules to be able to control tracing from user |
286 | space. This is done by issuing the following commands. Note however |
287 | these commands load all LTT modules. Depending on what options you chose to |
288 | compile statically, you may not need to issue all these commands. |
289 | |
c8997124 |
290 | <PRE> |
c924c2c6 |
291 | modprobe ltt-trace-control |
292 | modprobe ltt-marker-control |
293 | modprobe ltt-tracer |
294 | modprobe ltt-serialize |
295 | modprobe ltt-relay |
296 | modprobe ipc-trace |
297 | modprobe kernel-trace |
298 | modprobe mm-trace |
299 | modprobe net-trace |
300 | modprobe fs-trace |
301 | modprobe jbd2-trace |
302 | modprobe ext4-trace |
303 | modprobe syscall-trace |
304 | modprobe trap-trace |
305 | #if locking tracing is wanted, uncomment the following |
306 | #modprobe lockdep-trace |
c8997124 |
307 | </PRE> |
c924c2c6 |
308 | |
c8997124 |
309 | <p> |
c924c2c6 |
310 | If you want to have complete information about the kernel state (including all |
311 | the process names), you need to load the ltt-statedump module. This is done by |
312 | issuing the command : |
313 | |
c8997124 |
314 | <PRE> |
c924c2c6 |
315 | modprobe ltt-statedump |
c8997124 |
316 | </PRE> |
317 | <p> |
c924c2c6 |
318 | You can automate at boot time loading the ltt-control module by : |
319 | |
c8997124 |
320 | <PRE> |
c924c2c6 |
321 | cp /etc/modules /etc/modules.bkp |
322 | echo ltt-trace-control >> /etc/modules |
323 | echo ltt-marker-control >> /etc/modules |
324 | echo ltt-tracer >> /etc/modules |
325 | echo ltt-serialize >> /etc/modules |
326 | echo ltt-relay >> /etc/modules |
327 | echo ipc-trace >> /etc/modules |
328 | echo kernel-trace >> /etc/modules |
329 | echo mm-trace >> /etc/modules |
330 | echo net-trace >> /etc/modules |
331 | echo fs-trace >> /etc/modules |
332 | echo jbd2-trace >> /etc/modules |
333 | echo ext4-trace >> /etc/modules |
334 | echo syscall-trace >> /etc/modules |
335 | echo trap-trace >> /etc/modules |
336 | #if locking tracing is wanted, uncomment the following |
337 | #echo lockdep-trace >> /etc/modules |
c8997124 |
338 | </PRE> |
c924c2c6 |
339 | |
6f88b01d |
340 | |
341 | <h3><a href="#TOCgetlttctl" name="getlttctl">Getting and installing the |
342 | ltt-control package (on the traced machine)</a></h3> |
c8997124 |
343 | <p> |
c924c2c6 |
344 | (note : the ltt-control package contains lttd and lttctl. Although it has the |
345 | same name as the ltt-control kernel module, they are *not* the same thing.) |
c8997124 |
346 | |
347 | <PRE> |
c924c2c6 |
348 | su - |
349 | cd /usr/src |
350 | wget http://ltt.polymtl.ca/lttng/ltt-control-0.x-xxxx2006.tar.gz |
351 | gzip -cd ltt-control-0.x-xxxx2008.tar.gz | tar xvof - |
352 | cd ltt-control-0.x-xxxx2006 |
353 | (refer to README to see the development libraries that must be installed on you |
354 | system) |
355 | ./configure |
356 | make |
357 | make install |
c8997124 |
358 | </PRE> |
c924c2c6 |
359 | |
38b04cd7 |
360 | <h3><a href="#TOCuserspacetracing" name="userspacetracing">Userspace tracing</a></h3> |
c924c2c6 |
361 | |
c8997124 |
362 | <PRE> |
c924c2c6 |
363 | Make sure you selected the kernel menuconfig option : |
364 | <M> or <*> Support logging events from userspace |
365 | And that the ltt-userspace-event kernel module is loaded if selected as a |
366 | module. |
367 | |
368 | Simple userspace tracing is available through |
369 | echo "some text to record" > /mnt/debugfs/ltt/write_event |
370 | |
371 | It will appear in the trace under event : |
372 | channel : userspace |
373 | event name : event |
c8997124 |
374 | </PRE> |
c924c2c6 |
375 | |
6f88b01d |
376 | <h3><a href="#TOCgetlttv" name="getlttv">Getting and installing the LTTV package |
377 | (on the visualisation machine, same |
378 | or different from the visualisation machine)</a></h3> |
c924c2c6 |
379 | |
c8997124 |
380 | <PRE> |
c924c2c6 |
381 | su - |
382 | cd /usr/src |
383 | wget http://ltt.polymtl.ca/packages/lttv-0.x.xx-xxxx2008.tar.gz |
384 | gzip -cd lttv-0.x.xx-xxxx2008.tar.gz | tar xvof - |
385 | cd lttv-0.x.xx-xxxx2008 |
386 | (refer to README to see the development libraries that must be installed on your |
387 | system) |
388 | ./configure |
389 | make |
390 | make install |
13d7a628 |
391 | </PRE> |
c924c2c6 |
392 | |
c8997124 |
393 | <hr /> |
c924c2c6 |
394 | |
c924c2c6 |
395 | |
89aa576c |
396 | <h2><a href="#TOCsection2" name="section2">Using LTTng and LTTV</a></h2> |
c924c2c6 |
397 | |
d58b406f |
398 | <li><b>IMPORTANT : Arm Linux Kernel Markers after each boot before tracing</b></li> |
c8997124 |
399 | <PRE> |
c924c2c6 |
400 | ltt-armall |
c8997124 |
401 | </PRE> |
c924c2c6 |
402 | |
d58b406f |
403 | <h3><a href="#TOCuselttvgui" name="uselttvgui">Use graphical LTTV to control |
404 | tracing and analyse traces</a></h3> |
c8997124 |
405 | <PRE> |
c924c2c6 |
406 | lttv-gui (or /usr/local/bin/lttv-gui) |
407 | - Spot the "Tracing Control" icon : click on it |
408 | (it's a traffic light icon) |
409 | - enter the root password |
410 | - click "start" |
411 | - click "stop" |
412 | - Yes |
413 | * You should now see a trace |
c8997124 |
414 | </PRE> |
c924c2c6 |
415 | |
d58b406f |
416 | <h3><a href="#TOCuselttngtext" name="uselttngtext">Use text mode LTTng to control tracing</a></h3> |
c8997124 |
417 | <PRE> |
c924c2c6 |
418 | The tracing can be controlled from a terminal by using the lttctl command (as |
419 | root). |
420 | |
421 | Start tracing : |
422 | |
423 | lttctl -C -w /tmp/trace1 trace1 |
424 | |
425 | Stop tracing and destroy trace channels : |
426 | |
427 | lttctl -D trace1 |
428 | |
429 | see lttctl --help for details. |
df7f63ab |
430 | </PRE> |
c8997124 |
431 | <p> |
c924c2c6 |
432 | (note : to see if the buffers has been filled, look at the dmesg output after |
433 | lttctl -R or after stopping tracing from the GUI, it will show an event lost |
434 | count. If it is the case, try using larger buffers. See lttctl --help to learn |
435 | how. lttv now also shows event lost messages in the console when loading a trace |
436 | with missing events or lost subbuffers.) |
437 | |
d58b406f |
438 | <h3><a href="#TOCuselttvtext" name="uselttvtext">Use text mode LTTV</a></h3> |
c8997124 |
439 | <p> |
c924c2c6 |
440 | Feel free to look in /usr/local/lib/lttv/plugins to see all the text and |
441 | graphical plugins available. |
c8997124 |
442 | <p> |
c924c2c6 |
443 | For example, a simple trace dump in text format is available with : |
c8997124 |
444 | <PRE> |
c924c2c6 |
445 | lttv -m textDump -t /tmp/trace |
c8997124 |
446 | </PRE> |
c8997124 |
447 | <p> |
448 | See lttv -m textDump --help for detailed command line options of textDump. |
c8997124 |
449 | <p> |
c924c2c6 |
450 | It is, in the current state of the project, very useful to use "grep" on the |
451 | text output to filter by specific event fields. You can later copy the timestamp |
452 | of the events to the clipboard and paste them in the GUI by clicking on the |
453 | bottom right label "Current time". Support for this type of filtering should |
454 | be added to the filter module soon. |
455 | |
d58b406f |
456 | <h3><a href="#TOChybrid" name="hybrid">Tracing in "Hybrid" mode</a></h3> |
c8997124 |
457 | <p> |
c924c2c6 |
458 | Starting from LTTng 0.5.105 and ltt-control 0.20, a new mode can be used : |
459 | hybrid. It can be especially useful when studying big workloads on a long period |
460 | of time. |
c8997124 |
461 | <p> |
c924c2c6 |
462 | When using this mode, the most important, low rate control information will be |
463 | recorded during all the trace by lttd (i.e. process creation/exit). The high |
464 | rate information (i.e. interrupt/traps/syscall entry/exit) will be kept in a |
465 | flight recorder buffer (now named flight-channelname_X). |
c8997124 |
466 | <p> |
c924c2c6 |
467 | The following lttctl commands take an hybrid trace : |
c8997124 |
468 | <p> |
c924c2c6 |
469 | Create trace channel, start lttd on normal channels, start tracing: |
c8997124 |
470 | <PRE> |
c924c2c6 |
471 | lttctl -C -w /tmp/trace2 -o channel.kernel.overwrite=1 trace2 |
c8997124 |
472 | </PRE> |
473 | <p> |
c924c2c6 |
474 | Stop tracing, start lttd on flight recorder channels, destroy trace channels : |
c8997124 |
475 | <PRE> |
c924c2c6 |
476 | lttctl -D -w /tmp/trace2 trace2 |
c8997124 |
477 | </PRE> |
478 | <p> |
c924c2c6 |
479 | Each "overwrite" channel is flight recorder channel. |
480 | |
d58b406f |
481 | |
482 | <h3><a href="#TOCflight" name="flight">Tracing in flight recorder mode</a></h3> |
c8997124 |
483 | <li>Flight recorder mode</li> |
c8997124 |
484 | <p> |
c924c2c6 |
485 | The flight recorder mode writes data into overwritten buffers for all channels, |
486 | including control channels, except for the facilities tracefiles. It consists of |
487 | setting all channels to "overwrite". |
c8997124 |
488 | <p> |
c924c2c6 |
489 | The following lttctl commands take a flight recorder trace : |
c8997124 |
490 | <PRE> |
c924c2c6 |
491 | lttctl -C -w /tmp/trace3 -o channel.all.overwrite=1 trace3 |
492 | ... |
493 | lttctl -D -w /tmp/trace3 trace3 |
c8997124 |
494 | </PRE> |
c924c2c6 |
495 | |
89aa576c |
496 | <hr /> |
497 | |
498 | |
499 | <h2><a href="#TOCsection3" name="section3">Adding new instrumentations with the |
500 | markers</a></h2> |
501 | <p> |
c924c2c6 |
502 | |
47e2b195 |
503 | <h3><a href="#TOCkerneltp" name="kerneltp">Adding kernel |
504 | instrumentation</a></h3> |
505 | |
89aa576c |
506 | <p> |
47e2b195 |
507 | See <a |
508 | href="http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=blob;f=Documentation/markers.txt">Documentation/markers.txt</a> |
509 | and <a |
510 | href="http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=blob;f=Documentation/tracepoints.txt">Documentation/tracepoints.txt</a> in your kernel |
c924c2c6 |
511 | tree. |
47e2b195 |
512 | <p> |
513 | Also see <a |
514 | href="http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=tree;f=ltt/probes">ltt/probes/</a> |
515 | for LTTng probe examples. |
516 | |
517 | <h3><a href="#TOCusertp" name="usertp">Adding userspace instrumentation</a></h3> |
c924c2c6 |
518 | |
305fd815 |
519 | Add new events to userspace programs with |
520 | <a href="http://ltt.polymtl.ca/packages/">userspace markers packages</a>. |
c924c2c6 |
521 | Get the latest markers-userspace-*.tar.bz2 and see the Makefile and examples. It |
522 | allows inserting markers in executables and libraries, currently only on x86_32 |
523 | and x86_64. |
e01a1ce1 |
524 | See <a |
525 | href="http://ltt.polymtl.ca/packages/markers-userspace-0.5.tar.bz2">markers-userspace-0.5.tar.bz2</a> or more recent. |
526 | |
38b04cd7 |
527 | <p> |
e01a1ce1 |
528 | Note that a new design document for a 3rd generation of tracepoint/marker-based |
529 | userspace tracing is available at <a |
530 | href="http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/ust.html">LTTng User-space Tracing |
98dde887 |
531 | Design</a>. This new infrastructure is not yet implemented. |
38b04cd7 |
532 | |
533 | <p> |
534 | The easy quick-and-dirty way to perform userspace tracing is currently to write |
535 | an string to /mnt/debugfs/ltt/write_event. See <a |
536 | href="#userspacetracing">Userspace tracing</a> in the |
537 | installation for sources section of this document. |
e01a1ce1 |
538 | |
89aa576c |
539 | <hr /> |
633bc4a3 |
540 | |
89aa576c |
541 | <h2><a href="#TOCsection4" name="section4">Creating Debian or RPM packages</a></h2> |
542 | <p> |
633bc4a3 |
543 | |
98dde887 |
544 | <h3><a href="#TOCpkgdebian" name="pkgdebian">Create custom LTTV Debian packages</a></h3> |
633bc4a3 |
545 | |
89aa576c |
546 | <PRE> |
547 | Use : dpkg-buildpackage -rfakeroot |
548 | </PRE> |
549 | <p> |
633bc4a3 |
550 | You should then have your LTTV .deb files created for your architecture. |
551 | |
98dde887 |
552 | <h3><a href="#TOCpkglttng" name="pkglttng">Create custom LTTng packages</a></h3> |
89aa576c |
553 | <p> |
633bc4a3 |
554 | For building LTTng Debian packages : |
89aa576c |
555 | get the build tree with patches applies as explained in section 2. |
633bc4a3 |
556 | |
89aa576c |
557 | <PRE> |
633bc4a3 |
558 | make menuconfig (or xconfig or config) (customize your configuration) |
559 | make-kpkg kernel_image |
89aa576c |
560 | </PRE> |
561 | <p> |
633bc4a3 |
562 | You will then see your freshly created .deb in /usr/src. Install it with |
89aa576c |
563 | <PRE> |
633bc4a3 |
564 | dpkg -i /usr/src/(image-name).deb |
89aa576c |
565 | </PRE> |
566 | <p> |
633bc4a3 |
567 | Then, follow the section "Editing the system wide configuration" in section 2. |
568 | |
70a3fc43 |
569 | <hr /> |
633bc4a3 |
570 | |
70a3fc43 |
571 | <h2><a href="#TOCsection5" name="section5">Examples of LTTng use in the field</a></h2> |
572 | <p> |
573 | A few examples of successful LTTng users : |
633bc4a3 |
574 | |
70a3fc43 |
575 | <ul> |
576 | <li> Google are deploying LTTng on their servers. They want to use it to |
577 | monitor their production servers (with flight recorder mode tracing) |
578 | and to help them solve hard to reproduce problems. They have had |
579 | success with such tracing approach to fix "rare disk delay" issues and |
580 | VM-related issues presented in this article : |
07e962a1 |
581 | <ul> |
83cebd38 |
582 | <li> <a href="http://ltt.polymtl.ca/papers/bligh-Reprint.pdf">Linux Kernel |
583 | Debugging on Google-sized clusters at Ottawa Linux |
584 | Symposium 2007</a> |
07e962a1 |
585 | </ul> |
70a3fc43 |
586 | <li> IBM Research have had problems with Commercial Scale-out applications, |
587 | which are being an increasing trend to split large server workloads. |
588 | They used LTTng successfully to solve a distributed filesystem-related |
589 | issue. It's presented in the same paper above. |
590 | |
591 | <li> Autodesk, in the development of their next-generation of Linux |
592 | audio/video edition applications, used LTTng extensively to solve |
593 | soft real-time issues they had. Also presented in the same paper. |
594 | |
595 | <li> Wind River included LTTng in their Linux distribution so their |
596 | clients, already familiar to Wind River own tracing solution in |
597 | VxWorks, car have the same kind of feature they have relied on for a |
598 | long time. |
599 | |
600 | <li> Montavista have integrated LTTng in their distribution for the same |
601 | reasons. It's used by Sony amongst others. |
602 | |
603 | <li> SuSE are currently integrating LTTng in their next SLES distribution, |
604 | because their clients asking for solutions which supports a kernel |
605 | closer to real-time need such tools to debug their problems. |
606 | |
607 | <li> A project between Ericsson, the Canadian Defense, NSERC and various |
608 | universities is just starting. It aims at monitoring and debugging |
609 | multi-core systems and provide automated and help user system behavior |
610 | analysis. |
611 | |
612 | <li> Siemens have been using LTTng internally for quite some time now. |
613 | </ul> |
c924c2c6 |
614 | </body> |
615 | </html> |