1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >Installing LTT kernel tracer
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE=
"Linux Trace Toolkit Viewer User Guide"
11 HREF=
"index.html"><LINK
13 TITLE=
"Getting started"
16 TITLE=
"Getting started"
19 TITLE=
"Installing LTT trace recording daemon"
20 HREF=
"x54.html"></HEAD
31 SUMMARY=
"Header navigation table"
40 >Linux Trace Toolkit Viewer User Guide
</TH
56 >Chapter
2. Getting started
</TD
77 >2.2. Installing LTT kernel tracer
</A
80 > The goal of this guide is not to describe the Linux Trace Toolkit project in
82 seperate project for now. It just gives pointers to the basic steps you must
83 take in order to generate a trace suitable for conversion.
86 > First, go to the
<A
87 HREF=
"http://ltt.polymtl.ca"
91 website, in the
"Patches for the Official LTT" section. Use the latest version
92 of patches available. The file name convention used goes like this :
93 aaaaaa-x.x--bbbbb-y.y.patch. That means a patch made for aaaaa, release x.x,
94 that adds bbbbb, release y.y to it. Notice the presence of the -- sign that
95 separates the
"from" field from the name of the patch applied. This way, it's
96 impossible to be mixed up on the specific sequence of patch application. I
97 suggest that you use the
"relayfs",
"ltt" and then
"md" patches. The
"md" patch
98 adds events useful to LTTV that are not in the official LTT.
101 > Once you have the patches you need, get the matching Linux kernel version, apply
102 the patches on it, configure it, install it, reboot with the new kernel. You then
103 have an instrumented kernel ready for tracing. If you have problems during this phase,
105 HREF=
"http://www.opersys.com/ltt"
107 >www.opersys.com/ltt
</A
109 instructions about how to recompile a kernel, see
111 HREF=
"http://www.tldp.org/HOWTO/Kernel-HOWTO/"
122 SUMMARY=
"Footer navigation table"
175 >Installing LTT trace recording daemon
</TD