[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0809181050040.1034@wrl-59.cs.helsinki.fi>
Date: Thu, 18 Sep 2008 10:58:45 +0300 (EEST)
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To: Mike Galbraith <efault@....de>
cc: Ingo Molnar <mingo@...e.hu>,
Christoph Lameter <cl@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
kernel-testers@...r.kernel.org
Subject: Re: [Bug #11308] tbench regression on each kernel release from 2.6.22
-> 2.6.28
On Thu, 18 Sep 2008, Mike Galbraith wrote:
> On Thu, 2008-09-18 at 09:12 +0200, Mike Galbraith wrote:
>
> > 1e65e841bb5584136ed6047c55cf77532afbbb55 is first bad commit
> > commit 1e65e841bb5584136ed6047c55cf77532afbbb55
> > Author: Mike Galbraith <efault@....de>
> > Date: Wed Sep 17 14:55:50 2008 +0200
> >
> > Revert "Revert "block: export "ro" attribute""
> >
> > This reverts commit 2c8803af5c1bf41200167f29349f7f1396683a51.
>
> BTW, the reason it's revert revert is that I reverse bisected the revert
> tree yesterday, and it emitted the same darn result. I immediately said
> "yeah right, ya screwed up", and created the revert revert tree to make
> sure I couldn't fumble negation.
:-)
gcc compiling something slightly differently would be a nice theory but
it sort of breaks down now as this commit touches only one .c file...
In the past when I did some static inline .h -> .c uninline sizing tests
I noticed that some changes happened also in places which should have been
quite much unrelated. Though all the changes were minor anyway (in the
places I did look), e.g., routed the conditional paths slightly
differently and added one xor clear reg.
--
i.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists