[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJvTdK=9DVxY9xWCo=SSF-Rx3dFfZtkrubhtcgxxowj-rbi8LQ@mail.gmail.com>
Date: Sat, 7 Dec 2013 11:45:42 -0500
From: Len Brown <lenb@...nel.org>
To: Mike Galbraith <bitbucket@...ine.de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Linux PM list <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jeremy Eder <jeder@...hat.com>, x86@...nel.org
Subject: Re: 50 Watt idle power regression bisected to Linux-3.10
>> It fixes that, except for my Q6600 box. Too bad mwait_idle() went away,
>> beloved old box doesn't play hints game, so it continues to flog itself.
Thanks for pointing this out, Mike!
A Q6600 is a Kentsfield. I dug one of those up.
Indeed, the only idle capabilities it has are HALT
and old style MWAIT, and the latter is much more effective.
running 3.8 it idles at 75 watts.
running 3.8 with idle=nomwait it idles at 100 watts,
which is what it will do with 3.9 and later due to the patch below.
commit 69fb3676df3329a7142803bb3502fa59dc0db2e3
Author: Len Brown <len.brown@...el.com>
Date: Sun Feb 10 01:38:39 2013 -0500
x86 idle: remove mwait_idle() and "idle=mwait" cmdline param
Kentsfield proves that patch was based on a fault assumption.
Sweet box in its day, ECC memory and everything -- probably still
a fair number of them running...
Plus, I've found another machine that depends on having an idle=mwait
idle loop (A Sony Vaio BIOS SMM code apparently assumes we use it in
https://bugzilla.kernel.org/show_bug.cgi?id=60770)
So it looks like I need to (also) restore the simple idle=mwait idle loop
to make some machines happy.
thanks,
Len Brown, Intel Open Source Technology Center
--
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