From: Ingo Molnar <mingo@kernel.org>
To: Ian Malone <ibmalone@gmail.com>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Len Brown <lenb@kernel.org>,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
Josh Boyer <jwboyer@redhat.com>,
stable@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH REGRESSION FIX] x86 idle: restore mwait_idle()
Date: Tue, 17 Mar 2015 09:22:03 +0100 [thread overview]
Message-ID: <20150317082203.GC28462@gmail.com> (raw)
In-Reply-To: <CAL3-7Mo_OFdHdGDXq61eNuSqYaQiiGeBWsuGiSBsfcxSa2xExQ@mail.gmail.com>
* Ian Malone <ibmalone@gmail.com> wrote:
> On 15 March 2015 at 04:53, Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> > On Sat, 2015-03-14 at 23:44 +0000, Ian Malone wrote:
> >> On 18 January 2014 at 16:14, Mike Galbraith <bitbucket@online.de> wrote:
> >> > On Sat, 2014-01-18 at 10:33 +0100, Mike Galbraith wrote:
> >> >> On Fri, 2014-01-17 at 05:20 +0100, Mike Galbraith wrote:
> >>
> >> > Signed-off-by: Mike Galbraith <bitbucket@online.de>
> >> > Cc: <stable@vger.kernel.org> # 3.10+
> >> > ---
> >> > arch/x86/kernel/process.c | 9 ++++++---
> >> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >> >
> >> > --- a/arch/x86/kernel/process.c
> >> > +++ b/arch/x86/kernel/process.c
> >> > @@ -427,18 +427,21 @@ static int prefer_mwait_c1_over_halt(con
> >>
> >> Hi, this series of patches never seem to have made it as far as the
> >> mainline kernel, anyone know what needs to happen next?
> >
> > My plan is to keep on carrying it locally for as long as I run new
> > kernels on crusty ole core2 boxen, then stop caring about them entirely
> > like the rest of the planet :)
> >
>
> Looks like Ingo Molnar has committed to tip which is probably a good
> sign, thanks all.
> (Have to hand this system on to someone who wont be patching kernels...)
Guys, since I don't have the affected hardware, mind testing the
latest sched/core tree:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
cd tip
git checkout sched/core
# build a test kernel and boot it
Or if you already have a kernel git tree, do something like this to
pick up the scheduler development tree:
cd linux.git
git remote add git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tip
git remote update
git checkout tip/sched/core
# build a test kernel and boot it
and check whether the mwait related bugs are now fixed for good?
Thanks,
Ingo
next prev parent reply other threads:[~2015-03-17 8:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ae2a8af42281d6b9888ac8c76bab7bd2f431d44.1389763084.git.len.brown@intel.com>
2014-01-15 5:37 ` [PATCH REGRESSION FIX] x86 idle: restore mwait_idle() Len Brown
2014-01-15 9:28 ` Mike Galbraith
2014-01-16 22:00 ` Andy Lutomirski
2014-01-17 4:20 ` Mike Galbraith
2014-01-18 9:33 ` Mike Galbraith
2014-01-18 16:14 ` Mike Galbraith
2015-03-14 23:44 ` Ian Malone
2015-03-15 4:53 ` Mike Galbraith
2015-03-16 23:32 ` Ian Malone
2015-03-17 8:22 ` Ingo Molnar [this message]
2015-03-17 8:33 ` Mike Galbraith
2015-03-18 1:55 ` Ian Malone
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=20150317082203.GC28462@gmail.com \
--to=mingo@kernel.org \
--cc=ibmalone@gmail.com \
--cc=jwboyer@redhat.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=umgwanakikbuti@gmail.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).