From: Mike Galbraith <efault@gmx.de>
To: Lin Ming <ming.m.lin@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
venkatesh.pallipadi@intel.com, Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f
Date: Mon, 22 Feb 2010 05:59:22 +0100 [thread overview]
Message-ID: <1266814762.6072.3.camel@marge.simson.net> (raw)
In-Reply-To: <1266652377.3464.6.camel@minggr.sh.intel.com>
On Sat, 2010-02-20 at 15:52 +0800, Lin Ming wrote:
> On Mon, 2010-02-01 at 16:04 +0800, Mike Galbraith wrote:
> > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > >
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.32. Please verify if it still should be listed and let me know
> > > (either way).
> >
> > Yes, it should remain open. We're currently waiting for some data from
> > Lin Ming. The regression itself isn't making much sense.. a kernel with
> > NEWIDLE disabled should show the same performance, but does not.
>
> (sorry for late response, I'm just back from vacation)
>
> We finally located this to a bug in mwait based C-state entry.
> Venki's patch has fixed it.
> http://patchwork.kernel.org/patch/78544/
>
> Venki, this is the original report,
> http://marc.info/?l=linux-kernel&m=126441481427331&w=4
Excellent, mystery solved. (adds acpi)
-Mike
prev parent reply other threads:[~2010-02-22 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki
[not found] ` <d3IDKWHT5gE.A.Z-B.V7hZLB@chimera>
[not found] ` <1265011447.6220.15.camel@marge.simson.net>
[not found] ` <1266652377.3464.6.camel@minggr.sh.intel.com>
2010-02-22 4:59 ` Mike Galbraith [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=1266814762.6072.3.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=kernel-testers@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=venkatesh.pallipadi@intel.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