Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng roadmap (updated)
Date: Mon, 12 Jan 2009 12:06:48 -0500	[thread overview]
Message-ID: <20090112170648.GA27923@Krystal> (raw)
In-Reply-To: <20090107165606.GB3221@redhat.com>

* Jason Baron (jbaron at redhat.com) wrote:
> On Mon, Dec 15, 2008 at 06:59:12PM -0500, Mathieu Desnoyers wrote:
> > Well well, let's see what we have left to do before releasing LTTng to
> > LKML :
> > 
> 
> hi,
> 
> I find these roadmap updates quite helpful, thanks.
> 
> I was just wondering what the merge plans were for 2.6.29 merge window?
> Specifically, I'd (and I think others as well) are interested in the tracepoints 
> themselves, as found in include/trace/*.h and their respective source file 
> locations. In addition to lttng, Systemtap, and even simple ftrace
> widgets would make use of these.
> 

Hi Jason,

Linus has been very clear at OLS on that he does not want to merge
instrumentation if there is no tool that does *something* useful with
it.

AFAIK, Systemtap does not support getting tracepoints fields, am I
correct ?

We already merged the sched.h tracepoints because we have simple ftrace
widgets.

LTTng consists of many probe modules which expand the tracepoint
parameters into meaningful event data. They can also be the location for
probe-specific filtering (see the ext4 probe I just did for an example).
Those tracepoints have no other known users and therefore I plan to
submit the LTTng probing/buffering/trace control infrastructure before I
submit the tracepoints.

Best regards,

Mathieu


> thanks,
> 
> -Jason
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68



      reply	other threads:[~2009-01-12 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 23:59 Mathieu Desnoyers
2009-01-07 16:56 ` Jason Baron
2009-01-12 17:06   ` Mathieu Desnoyers [this message]

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=20090112170648.GA27923@Krystal \
    --to=compudj@krystal.dyndns.org \
    /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