linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Li Zefan <lizf@cn.fujitsu.com>, Jeff Moyer <jmoyer@redhat.com>,
	Ingo Molnar <mingo@elte.hu>, Jens Axboe <jens.axboe@oracle.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Tom Zanussi <tzanussi@gmail.com>, "Theodore Ts'o" <tytso@mit.edu>,
	Steven Whitehouse <swhiteho@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] convert block trace points to TRACE_EVENT()
Date: Sun, 24 May 2009 04:57:01 -0400	[thread overview]
Message-ID: <20090524085701.GA4302@infradead.org> (raw)
In-Reply-To: <20090524141347.0841.A69D9226@jp.fujitsu.com>

On Sun, May 24, 2009 at 02:15:05PM +0900, KOSAKI Motohiro wrote:
> > Is there any good reason for keeping the ftrace plugin once we have
> > the fully function event tracer support for the block events?
> 
> waiting userland blktrace tool convert using event tracer? 

blktrace(8) uses the ioctl interface, which we should keep for a long
time for backwards compatiblity.  


  reply	other threads:[~2009-05-24  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14  6:20 [RFC][PATCH] convert block trace points to TRACE_EVENT() Li Zefan
2009-05-18  8:35 ` Ingo Molnar
2009-05-19  6:04   ` Li Zefan
2009-05-18 13:05 ` Frederic Weisbecker
2009-05-19  6:11   ` Li Zefan
2009-05-19 12:59 ` Jeff Moyer
2009-05-19 13:08   ` Christoph Hellwig
2009-05-19 15:49     ` FUJITA Tomonori
2009-05-19 17:33       ` Jens Axboe
2009-05-20  8:38     ` Li Zefan
2009-05-23 12:40       ` Christoph Hellwig
2009-05-24  5:15         ` KOSAKI Motohiro
2009-05-24  8:57           ` Christoph Hellwig [this message]
2009-05-24 13:47             ` 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=20090524085701.GA4302@infradead.org \
    --to=hch@infradead.org \
    --cc=fweisbec@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=jmoyer@redhat.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=swhiteho@redhat.com \
    --cc=tytso@mit.edu \
    --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;
as well as URLs for NNTP newsgroup(s).