public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] blktrace: last round of fixes
Date: Mon, 30 Mar 2009 03:23:37 +0200	[thread overview]
Message-ID: <20090330012337.GC11087@elte.hu> (raw)
In-Reply-To: <49D014F9.8000404@cn.fujitsu.com>


* Li Zefan <lizf@cn.fujitsu.com> wrote:

> Ingo Molnar wrote:
> > * Li Zefan <lizf@cn.fujitsu.com> wrote:
> > 
> >> This is the last round of fixes for blktrace, I hope.  :) 
> >>
> >> Changelog v1 -> v2:
> >>   - fix a bug in "blktrace: make classic output more classic",
> >>     and rebase other patches.
> >>   - re-order patches.
> >>   - a new patch for filtering BLK_TN_MESSAGE
> >>
> >> [PATCH v2 1/6] trace: make 'mem' argument of trace_seq_putmem() const
> >> [PATCH v2 2/6] blktrace: make classic output more classic
> >> [PATCH v2 3/6] blktrace: fix blk_probes_ref chaos
> >> [PATCH v2 4/6] blktrace: fix memory leak when freeing struct blk_io_trace
> >> [PATCH v2 5/6] blktrace: extract duplidate code
> >> [PATCH v2 6/6] blktrace: print out BLK_TN_MESSAGE properly
> >> ---
> >>  blktrace.c     |  188 +++++++++++++++++++++++++++++++++------------------------
> >>  trace_output.c |    6 -
> >>  trace_output.h |    5 -
> >>  3 files changed, 117 insertions(+), 82 deletions(-)
> > 
> > Li, Jens - what's your call for v2.6.30, can the blktrace changes go 
> > upstream or should i zap the whole thing?
> > 
> 
> It should be fine to merge tip/blktrace into .30, and we still 
> have 2 month to fix remaining bugs, if any.

ok.

Although regarding instrumentation patches we carry in -tip we aim 
to enforce perfect stability right at the point of the merge window. 

One major point of instrumentation is to find kernel bugs ... and 
it's self-defeating if instrumentation is buggy itself! By the time 
the stable kernel is released the most important kernel bugs are 
fixed already so having stable instrumentation by that moment is too 
late.

So we've got extensive self-tests and other measures in place to 
ensure stability.

( The mixed blktrace ioctl/ftrace plugin usage model fell a bit
  outside of the expectation of these stability tests though, hence
  this relatively slow and late stabilization curve there. It still 
  looks all fine for .30 to me too. )

	Ingo

      reply	other threads:[~2009-03-30  1:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  5:39 [PATCH v2 0/7] blktrace: last round of fixes Li Zefan
2009-03-27  5:39 ` [PATCH v2 1/7] trace: make 'mem' argument of trace_seq_putmem() const Li Zefan
2009-03-27  5:40 ` [PATCH v2 2/7] blktrace: make classic output more classic Li Zefan
2009-03-27  5:40 ` [PATCH v2 3/7] blktrace: fix blk_probes_ref chaos Li Zefan
2009-03-27  8:13   ` [PATCH v3 " Li Zefan
2009-03-27  5:40 ` [PATCH v2 4/7] blktrace: fix memory leak when freeing struct blk_io_trace Li Zefan
2009-03-27  8:13   ` [PATCH v3 " Li Zefan
2009-03-27  5:41 ` [PATCH v2 5/7] blktrace: extract duplidate code Li Zefan
2009-03-27  5:41 ` [PATCH v2 6/7] blktrace: print out BLK_TN_MESSAGE properly Li Zefan
2009-03-27  5:42 ` [PATCH v2 7/7] blktrace: support filtering of BLK_TN_MESSAGE Li Zefan
2009-03-27  9:42 ` [PATCH v2 0/7] blktrace: last round of fixes Ingo Molnar
2009-03-28 22:46 ` Ingo Molnar
2009-03-29 18:02   ` Jens Axboe
2009-03-30  1:17     ` Ingo Molnar
2009-03-30  0:40   ` Li Zefan
2009-03-30  1:23     ` Ingo Molnar [this message]

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=20090330012337.GC11087@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.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