From: Len Brown <lenb@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: linux-pm@lists.linux-foundation.org, stable@kernel.org
Subject: Re: [stable] [PATCH 1/2 2.6.37.stable] intel_idle: disable NHM/WSM HW C-state auto-demotion
Date: Wed, 23 Mar 2011 22:53:22 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1103232252000.12911@x980> (raw)
In-Reply-To: <20110323225420.GE27334@kroah.com>
On Wed, 23 Mar 2011, Greg KH wrote:
> On Tue, Mar 22, 2011 at 10:24:43PM -0400, Len Brown wrote:
> > From: Len Brown <len.brown@intel.com>
> >
> > upstream 14796fca2bd22acc73dd0887248d003b0f441d08
> >
> > Hardware C-state auto-demotion is a mechanism where the HW overrides
> > the OS C-state request, instead demoting to a shallower state,
> > which is less expensive, but saves less power.
> >
> > Modern Linux should generally get exactly the states it requests.
> > In particular, when a CPU is taken off-line, it must not be demoted, else
> > it can prevent the entire package from reaching deep C-states.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=25252
> >
> > Signed-off-by: Len Brown <len.brown@intel.com>
>
> This patch doesn't apply to the .38-stable tree, and it also needs to go
> there, right? Can you please send a version that I can apply?
it is already present in 2.6.38, as is the next one.
That is why the subject specified 2.6.37.stable.
thanks,
-Len
next prev parent reply other threads:[~2011-03-24 2:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 2:24 [PATCH 1/2 2.6.37.stable] intel_idle: disable NHM/WSM HW C-state auto-demotion Len Brown
2011-03-23 2:26 ` [PATCH 2/2 2.6.37.stable] intel_idle: disable Atom/Lincroft " Len Brown
2011-03-23 22:55 ` [stable] " Greg KH
2011-03-23 22:54 ` [stable] [PATCH 1/2 2.6.37.stable] intel_idle: disable NHM/WSM " Greg KH
[not found] ` <20110323225420.GE27334@kroah.com>
2011-03-24 2:53 ` Len Brown [this message]
2011-03-24 3:39 ` Greg KH
2011-04-08 13:16 ` Pavel Machek
2011-04-08 16:14 ` Len Brown
2011-04-08 13:16 ` Pavel Machek
2011-04-08 22:31 ` Len Brown
2011-04-15 16:25 ` Pavel Machek
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=alpine.LFD.2.02.1103232252000.12911@x980 \
--to=lenb@kernel.org \
--cc=greg@kroah.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stable@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