All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: David Dillow <dillowda@ornl.gov>,
	Guillaume Chazarain <guichaz@yahoo.fr>,
	linux-kernel@vger.kernel.org, linux-btrace@vger.kernel.org,
	mingo@redhat.com, tglx@linutronix.de,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] block: fix blktrace timestamps
Date: Mon, 14 Jan 2008 07:59:22 +0000	[thread overview]
Message-ID: <20080114075922.GA17686@elte.hu> (raw)
In-Reply-To: <20080114075114.GA13195@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> because a perfectly working system is:
> 
>  "a user's .config that worked before should work with the new kernel
>   too"
> 
> not:
> 
>  "a user's .config that worked before should work now too, with random
>   new kernel features enabled as well."
> 
> the latter appears to be the rule you are applying, but it's not the 
> regression rule we are using.

Jens, just to bring your definition of regressions to its logical 
conclusion: does this mean that if there is any longstanding bug in the 
block layer that you know about, but i didnt ever utilize that bit of 
the block layer it in my .config, and if i enable it now in the .config 
and i experience that bug, does it suddenly count as a regression? Do 
you realize that your definition for "regressions" turns _almost every_ 
current bug in the kernel into a regression?

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: David Dillow <dillowda@ornl.gov>,
	Guillaume Chazarain <guichaz@yahoo.fr>,
	linux-kernel@vger.kernel.org, linux-btrace@vger.kernel.org,
	mingo@redhat.com, tglx@linutronix.de,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] block: fix blktrace timestamps
Date: Mon, 14 Jan 2008 08:59:22 +0100	[thread overview]
Message-ID: <20080114075922.GA17686@elte.hu> (raw)
In-Reply-To: <20080114075114.GA13195@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> because a perfectly working system is:
> 
>  "a user's .config that worked before should work with the new kernel
>   too"
> 
> not:
> 
>  "a user's .config that worked before should work now too, with random
>   new kernel features enabled as well."
> 
> the latter appears to be the rule you are applying, but it's not the 
> regression rule we are using.

Jens, just to bring your definition of regressions to its logical 
conclusion: does this mean that if there is any longstanding bug in the 
block layer that you know about, but i didnt ever utilize that bit of 
the block layer it in my .config, and if i enable it now in the .config 
and i experience that bug, does it suddenly count as a regression? Do 
you realize that your definition for "regressions" turns _almost every_ 
current bug in the kernel into a regression?

	Ingo

  reply	other threads:[~2008-01-14  7:59 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 22:48 CONFIG_NO_HZ breaks blktrace timestamps David Dillow
2008-01-09 22:48 ` David Dillow
2008-01-10 20:25 ` David Dillow
2008-01-10 20:25   ` David Dillow
2008-01-10 22:44   ` Guillaume Chazarain
2008-01-10 22:44     ` Guillaume Chazarain
2008-01-11  3:04     ` David Dillow
2008-01-11  3:04       ` David Dillow
2008-01-11  9:07       ` Jens Axboe
2008-01-11  9:07         ` Jens Axboe
2008-01-11  9:23         ` Ingo Molnar
2008-01-11  9:23           ` Ingo Molnar
2008-01-11  9:25           ` Jens Axboe
2008-01-11  9:25             ` Jens Axboe
2008-01-11  9:42             ` Ingo Molnar
2008-01-11  9:42               ` Ingo Molnar
2008-01-11  9:56               ` Jens Axboe
2008-01-11  9:56                 ` Jens Axboe
2008-01-11 10:29                 ` [patch] block: fix " Ingo Molnar
2008-01-11 10:29                   ` Ingo Molnar
2008-01-11 10:47                   ` Guillaume Chazarain
2008-01-11 10:47                     ` Guillaume Chazarain
2008-01-11 10:50                     ` Ingo Molnar
2008-01-11 10:50                       ` Ingo Molnar
2008-01-11 12:28                   ` Jens Axboe
2008-01-11 12:28                     ` Jens Axboe
2008-01-11 12:42                     ` Jens Axboe
2008-01-11 12:42                       ` Jens Axboe
2008-01-11 13:21                     ` Ingo Molnar
2008-01-11 13:21                       ` Ingo Molnar
2008-01-11 17:18                       ` Jens Axboe
2008-01-11 17:18                         ` Jens Axboe
2008-01-14  7:51                         ` Ingo Molnar
2008-01-14  7:51                           ` Ingo Molnar
2008-01-14  7:59                           ` Ingo Molnar [this message]
2008-01-14  7:59                             ` Ingo Molnar
2008-01-14  8:10                             ` Jens Axboe
2008-01-14  8:10                               ` Jens Axboe
2008-01-14  8:39                           ` Christoph Hellwig
2008-01-14  8:42                             ` Jens Axboe
2008-01-14  8:42                               ` Jens Axboe
2008-01-11 15:36                   ` David Dillow
2008-01-11 15:36                     ` David Dillow
2008-01-11 16:44                     ` Ingo Molnar
2008-01-11 16:44                       ` Ingo Molnar
2008-01-11 17:26                       ` Jens Axboe
2008-01-11 17:26                         ` Jens Axboe
2008-01-11  9:29           ` CONFIG_NO_HZ breaks " Ingo Molnar
2008-01-11  9:29             ` Ingo Molnar
2008-01-11  9:34             ` Jens Axboe
2008-01-11  9:34               ` Jens Axboe
2008-01-11  9:28         ` nigel
2008-01-11  9:28           ` nigel
2008-01-11  9:32           ` Ingo Molnar
2008-01-11  9:32             ` Ingo Molnar
2008-01-13 22:54             ` nigel
2008-01-13 22:54               ` nigel
2008-01-11  9:44       ` Ingo Molnar
2008-01-11  9:44         ` Ingo Molnar
2008-01-11  9:51         ` Ingo Molnar
2008-01-11  9:51           ` Ingo Molnar
2008-01-11 10:41     ` Guillaume Chazarain
2008-01-11 10:41       ` Guillaume Chazarain
2008-01-11 10:55       ` Ingo Molnar
2008-01-11 10:55         ` Ingo Molnar
2008-01-11 22:30         ` Guillaume Chazarain
2008-01-11 22:30           ` Guillaume Chazarain
2008-01-12  0:03           ` Guillaume Chazarain
2008-01-12  0:03             ` Guillaume Chazarain
2008-01-11  9:34   ` Ingo Molnar
2008-01-11  9:34     ` Ingo Molnar
2008-01-11 15:43     ` David Dillow
2008-01-11 15:43       ` David Dillow

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=20080114075922.GA17686@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=dillowda@ornl.gov \
    --cc=guichaz@yahoo.fr \
    --cc=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.