Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Matt.Schreiner@zoran.com (Matt Schreiner)
Subject: [ltt-dev] general installation help
Date: Mon, 1 Nov 2010 21:09:49 +0000	[thread overview]
Message-ID: <52E6371B02447449947E563642EB32023B4FA9FB@zcomb2.Zoran.com> (raw)
Message-ID: <20101101210949.Miju82zrg6ax1qLJfo0SCmygc3zWgEMyBRf1qXAg7bk@z> (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/ltt-dev/attachments/20101101/a7b2ebbd/attachment.htm>


             reply	other threads:[~2010-11-01 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 21:09 Matt Schreiner [this message]
2010-11-01 21:09 ` Matt Schreiner
2010-11-01 21:09 ` Matt Schreiner
2010-11-03 15:17 ` Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52E6371B02447449947E563642EB32023B4FA9FB@zcomb2.Zoran.com \
    --to=matt.schreiner@zoran.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox