From: Li Zefan <lizf@cn.fujitsu.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Steven Whitehouse" <swhiteho@redhat.com>,
"Tom Zanussi" <tzanussi@gmail.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, axboe@kernel.dk
Subject: Re: Multiple Tracers
Date: Thu, 09 Apr 2009 11:12:17 +0800 [thread overview]
Message-ID: <49DD6791.2010507@cn.fujitsu.com> (raw)
In-Reply-To: <20090409025507.GB24946@ghostprotocols.net>
>>> Tom Zanussi (Cc:-ed) recently converted the blktrace tracepoints to
>> I guess you mean Arnaldo <acme@redhat.com> ;)
>
> Nope, Tom:
>
> Message-Id: <1235725261.8512.89.camel@charm-linux>
>
Ah, sorry for the mistake, I didn't notice that patch, and I thought
Ingo meant the ftrace-plugin patch.
>>> 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.
>>>
>> Actually we've planed to do this, and for other tracers.
>
> Yeah, being able to mix all kinds of tracers is the way to go.
>
next prev parent reply other threads:[~2009-04-09 3:11 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
2009-04-09 2:11 ` Li Zefan
2009-04-09 2:55 ` Arnaldo Carvalho de Melo
2009-04-09 3:12 ` Li Zefan [this message]
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=49DD6791.2010507@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=acme@redhat.com \
--cc=axboe@kernel.dk \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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