From: Steven Whitehouse <swhiteho@redhat.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, axboe@kernel.dk
Subject: Multiple Tracers
Date: Wed, 08 Apr 2009 14:35:03 +0100 [thread overview]
Message-ID: <1239197703.3359.25.camel@localhost.localdomain> (raw)
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.
Is there a solution to this which I've not spotted, or would something
along the lines of my previous patch[*] be a reasonable solution at this
stage?
Steve.
[*] http://markmail.org/message/ujkd6bre2td27pfb
next reply other threads:[~2009-04-08 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 13:35 Steven Whitehouse [this message]
2009-04-08 13:53 ` Multiple Tracers Ingo Molnar
2009-04-08 14:11 ` Steven Whitehouse
2009-04-08 14:24 ` Ingo Molnar
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=1239197703.3359.25.camel@localhost.localdomain \
--to=swhiteho@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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