From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] Enable bit 11 in _PDC to advertise hw coord
Date: Wed, 4 Feb 2009 17:53:31 -0200 [thread overview]
Message-ID: <20090204195331.GA905@khazad-dum.debian.net> (raw)
In-Reply-To: <20090204085712.GF30821@kernel.dk>
On Wed, 04 Feb 2009, Jens Axboe wrote:
> On Mon, Feb 02 2009, Pallipadi, Venkatesh wrote:
> >
> > Bit 11 in intel PDC definitions is meant for OS capability to handle
> > hardware coordination of P-states. In Linux we have always supported
> > hwardware coordination of P-states. Just let the BIOSes know that we
> > support it, by setting this bit.
> >
> > Some BIOSes use this bit to choose between hardware or software coordination
> > and without this change below, BIOSes switch to software coordination, which
> > is not very optimal in terms of power consumption and extra wakeups from idle.
>
> I can confirm that this fixes the excessive reschedule ipi count on an
> x60 with the ondemand governor. Can we please get this into 2.6.29?
And, after that, -stable?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2009-02-04 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 19:57 [PATCH] Enable bit 11 in _PDC to advertise hw coord Pallipadi, Venkatesh
2009-02-04 8:57 ` Jens Axboe
2009-02-04 19:53 ` Henrique de Moraes Holschuh [this message]
2009-02-04 20:06 ` Pallipadi, Venkatesh
2009-02-04 20:40 ` Greg KH
2009-02-08 19:51 ` [stable] " Greg KH
2009-02-07 4:10 ` Len Brown
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=20090204195331.GA905@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=chris.mason@oracle.com \
--cc=jens.axboe@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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