From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
ltt-dev@lists.casi.polymtl.ca, Hideo AOKI <haoki@redhat.com>,
Takahiro Yasui <tyasui@redhat.com>,
systemtap-ml <systemtap@sources.redhat.com>
Subject: Re: [ltt-dev] [LTTng][RFC][Patch 2/2] add irq-id parameter to irq_exit tracepoint and marker
Date: Fri, 12 Sep 2008 17:38:00 -0000 [thread overview]
Message-ID: <20080912173753.GA27996@Krystal> (raw)
In-Reply-To: <48CA9C00.8020606@redhat.com>
* Masami Hiramatsu (mhiramat@redhat.com) wrote:
> Hi Mathieu,
>
> Mathieu Desnoyers wrote:
> >> And when we use these markers not from LTTng (ex. systemtap),
> >> it could be handled as isolated events. For example, I can check which
> >> irq handler returns error by tracing ONLY irq_exit events, with this patch.
> >>
> >
> > Hrm, this is precisely why I created the tracepoints. I would be all in
> > to add a struct pt_regs parameter and a irq id parameter to the irq exit
> > _tracepoint_ (since this is a kernel internal API), but I am very
> > reluctant to add it to the marker, given it will add useless information
> > in the traces.
>
> Indeed. What we really need is additional parameters for tracepoints, not
> markers, because markers can't get parameters which are not passed from
> tracepoints. ;-)
> LTTng's conversion module can filter those parameters for LTTng
> or some other tracers which use LTTng markers.
>
> > I propose that systemtap move to tracepoints instead of markers, given
> > that they run in kernel-space anyway. It'a really a plus to have correct
> > typing of pointers, structures, etc.
>
> The difficulty of using tracepoints directly is parsing native C
> code to get parameters. If each tracer can have its conversion module,
> I think we don't need to do so.
>
> >>> Here we need to compromise between the trace size and the amount of work
> >>> needed to analyze the trace. kernel_irq_exit is a very high rate event
> >>> and the work needed to keep track of the state is small. Therefore I
> >>> doubt including the redundant information is the best choice.
> >> Indeed, could LTTng ignores(or filters) the parameter?
> >>
> >
> > LTTng just parses the format string and dumps them to userspace. Since I
> > developed the tracepoints, I see more and more the markers as being a
> > "binary formatting" infrastructure more closely tied to LTTng. But
> > tracepoints are taking over, so there is no features removed, just added
> > flexibility for in-kernel tracers.
>
> BTW, if so, I think we can make various versions of tracepoint-marker
> conversion modules for LTTng and other in-kernel tracers.
>
> Thank you,
>
Yep, I agree. Could you rearrange your patch against LTTng
instrumentation to only add the irq exit tracepoint parameter you need ?
I would be glad to merge that,
Thanks,
Mathieu
>
> --
> Masami Hiramatsu
>
> Software Engineer
> Hitachi Computer Products (America) Inc.
> Software Solutions Division
>
> e-mail: mhiramat@redhat.com
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2008-09-12 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 15:39 Masami Hiramatsu
2008-08-26 16:40 ` [ltt-dev] " Pierre-Marc Fournier
2008-08-26 18:45 ` Masami Hiramatsu
2008-09-10 22:36 ` Mathieu Desnoyers
2008-09-12 16:45 ` Masami Hiramatsu
2008-09-12 17:38 ` Mathieu Desnoyers [this message]
2008-09-12 21:35 ` Masami Hiramatsu
2008-09-14 16:14 ` Ingo Molnar
2008-09-14 22:16 ` Masami Hiramatsu
2008-08-28 1:08 ` 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=20080912173753.GA27996@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=haoki@redhat.com \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=pierre-marc.fournier@polymtl.ca \
--cc=systemtap@sources.redhat.com \
--cc=tyasui@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).