public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Jan Blunck <jblunck@suse.de>,
	  ltt-dev Mailing List <ltt-dev@lists.casi.polymtl.ca>,
	  systemtap@sourceware.org
Subject: Re: [ltt-dev] [PATCH] tracepoints: Generate Module.tracepoints file
Date: Tue, 23 Sep 2008 02:56:00 -0000	[thread overview]
Message-ID: <20080923025332.GH24937@Krystal> (raw)
In-Reply-To: <y0mzlm0mbo6.fsf@ton.toronto.redhat.com>

* Frank Ch. Eigler (fche@redhat.com) wrote:
> Jan Blunck <jblunck@suse.de> writes:
> 
> > This adds support to generate the Module.tracepoints file by modpost. This
> > can be read by tools like SystemTap very similar to the Module.markers file.
> > [...]
> 
> For systemtap, the problem with tracepoints is not so much knowing the
> list of them, but knowing how to dynamically interface to them.  In
> particular, the parameter type signatures are a problem because they
> can be general C type decls, which are hard just to parse.
> 

Why would you want to deal with tracepoints dynamically ? They are meant
to be fixed in-kernel API. when an in-kernel API changes, you just adapt
the code accordingly. Therefore, I don't see why you would try to follow
these changes "automatically" ?

To me, it makes as much sense as trying to follow EXPORT_SYMBOL*() or
any kernel API automatically.

And remember, tracepoints are meant to be few, well thought and not to
cange too often once things settle down.

OTOH, markers can be used as temporary debugging statements, which makes
it understandable to follow their changes dynamically.

Mathieu

> - FChE
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev@lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

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

  reply	other threads:[~2008-09-23  2:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 15:09 Jan Blunck
2008-09-18 16:06 ` [ltt-dev] " Mathieu Desnoyers
2008-09-18 16:32   ` Jan Blunck
2008-09-18 17:26     ` Mathieu Desnoyers
2008-09-22 15:42 ` Frank Ch. Eigler
2008-09-23  2:56   ` Mathieu Desnoyers [this message]
2008-09-23 16:11     ` [ltt-dev] " Frank Ch. Eigler
2008-09-23 16:35       ` Mathieu Desnoyers
2008-09-23 18:09   ` KOSAKI Motohiro

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=20080923025332.GH24937@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=fche@redhat.com \
    --cc=jblunck@suse.de \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).