Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
* [ltt-dev] general installation help
@ 2010-11-01 21:09 Matt Schreiner
  2010-11-01 21:09 ` Matt Schreiner
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Matt Schreiner @ 2010-11-01 21:09 UTC (permalink / raw)


I recently downloaded Centos 5.5 (same as Red Hat 5.5?), based on 2.6.18 kernel.  I note that even at that revision, many of the kernel trace-points are in the code, and the kernel has been built with CONFIG_TRACEPOINTS=y, CONFIG_MARKERS=y, and CONFIG_SAMPLE_TRACEPOINTS=m.

My question is: will I be able to use LTTng without rebuilding the kernel?

I've downloaded  the following, aiming for the closest compatible with 2.6.18:

Genevent-0.31
Linuxtracetoolkitviewer-0.8.72-06122006
Ltt-control-0.31-20112006
Ltt-usertrace-0.21
Patch-2.6.18-lttng-0.6.41

Though ./configure does a lot of work in each of these projects, I'm missing an overall description of which pieces are needed, where they have to reside, and how to turn them on.  Is there a basic how-to manual?  The patches would imply that I have to rebuild the kernel, though it seemed they were all extensions to kernel header files, and patches to LTTng sources.

I'm also trying to use tracepoints for my own purposes, and my Linux box crashes hard when I call register_trace_sched_switch from a loadable module.  Any ideas how to debug this?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20101101/a7b2ebbd/attachment-0001.htm>


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-11-03 15:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-01 21:09 [ltt-dev] general installation help Matt Schreiner
2010-11-01 21:09 ` Matt Schreiner
2010-11-01 21:09 ` Matt Schreiner
2010-11-03 15:17 ` Mathieu Desnoyers

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox