From: Ingo Molnar <mingo@elte.hu>
To: "Steven Whitehouse" <swhiteho@redhat.com>,
"Tom Zanussi" <tzanussi@gmail.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, axboe@kernel.dk
Subject: Re: Multiple Tracers
Date: Wed, 8 Apr 2009 16:24:13 +0200 [thread overview]
Message-ID: <20090408142413.GF12931@elte.hu> (raw)
In-Reply-To: <1239199899.3359.39.camel@localhost.localdomain>
* Steven Whitehouse <swhiteho@redhat.com> wrote:
> Hi,
>
> On Wed, 2009-04-08 at 15:53 +0200, Ingo Molnar wrote:
> > * Steven Whitehouse <swhiteho@redhat.com> wrote:
> >
> > > Hi,
> > >
> > > A little while back I posted a RFC patch which added gfs2 glock
> > > tracing to blktrace. There was a suggestion that I should look
> > > instead at the generic tracing code and add a new tracer, but I've
> > > come up with a couple of issues along the way.
> > >
> > > I think from what I can see that its only possible to run a single
> > > tracer at once, so running blktrace (for example) would preclude
> > > me from also tracing gfs2's glocks at the same time. Also, I can
> > > see no mechanism by which I could ensure the sequencing between
> > > the blktrace and glock traces other than exporting the blktrace
> > > sequence number, even if running multiple tracers at the same time
> > > was possible.
> >
> > There's a recent addition: the EVENT_TRACE() facility. Would that
> > suit your purposes?
> >
> > Ingo
>
> If I can get both blktrace and glock trace info from it, then yes.
> I thought that the blktrace output went either via the original
> relayfs path, or via its own tracer so that it wasn't possible to
> use it and the event trace facility at the same time, unless I use
> blktrace via relayfs. From what I've read I thought that probably
> the relayfs interface for blktrace might eventually be removed in
> favour of the generic tracing interface, but I'm not 100% sure of
> that, so perhaps someone can confirm the plans in that area?
Tom Zanussi (Cc:-ed) recently converted the blktrace tracepoints to
a tracing framework - and i think much of that could be reused to
add EVENT_TRACE() tracepoints to blktrace too.
Tom, what's your take on this?
In general, this is the direction we want to take: EVENT_TRACE()
tracepoints that can be used in a generic way, in any tracer.
Ingo
next prev parent reply other threads:[~2009-04-08 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 13:35 Multiple Tracers Steven Whitehouse
2009-04-08 13:53 ` Ingo Molnar
2009-04-08 14:11 ` Steven Whitehouse
2009-04-08 14:24 ` Ingo Molnar [this message]
2009-04-09 2:11 ` Li Zefan
2009-04-09 2:55 ` Arnaldo Carvalho de Melo
2009-04-09 3:12 ` Li Zefan
2009-04-09 4:38 ` Ingo Molnar
2009-04-09 5:37 ` Tom Zanussi
2009-04-09 8:15 ` Steven Whitehouse
2009-04-08 14:13 ` Steven Rostedt
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=20090408142413.GF12931@elte.hu \
--to=mingo@elte.hu \
--cc=axboe@kernel.dk \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=swhiteho@redhat.com \
--cc=tzanussi@gmail.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