From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Len Brown <lenb@kernel.org>
Cc: "Pavel Troller" <patrol@sinus.cz>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
cpufreq@lists.linux.org.uk,
"Alex Villacís Lasso" <avillaci@ceibo.fiec.espol.edu.ec>,
linux-acpi@vger.kernel.org
Subject: Re: About p4-clockmod breakage/removal
Date: Wed, 14 May 2008 22:55:10 -0300 [thread overview]
Message-ID: <20080515015510.GD3415@khazad-dum.debian.net> (raw)
In-Reply-To: <200805141322.26879.lenb@kernel.org>
On Wed, 14 May 2008, Len Brown wrote:
> But the cost is that others with actual working hardware
> unnwittingly run p4-clockmod and slow down their machine with
> no energy savings benefit.
Well, there ARE ways to make sure p4-clockmod is only used as a last
ressort, and we CAN make sure the user will be told it is using a last
ressort measure that does not save energy. Major nasty printks come to
mind.
p4-clockmod has saved my bacon on an Intel D875PBZ motherboard whose
processor was overheating, as well (older kernel, though. That box runs
2.6.16.y). I can't check right now if that motherboard has proper ACPI
thermal zones that would do the same in a new kernel without
p4-clockmod, but I will do so when I have the chance.
--
"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:[~2008-05-15 1:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48246C3E.7010608@ceibo.fiec.espol.edu.ec>
2008-05-14 0:48 ` About p4-clockmod breakage/removal Len Brown
2008-05-14 0:56 ` Matthew Garrett
2008-05-14 3:35 ` Len Brown
2008-05-14 9:15 ` Matthew Garrett
2008-05-14 15:18 ` Len Brown
2008-05-14 23:11 ` Matthew Garrett
2008-05-14 11:18 ` Pavel Troller
2008-05-14 17:22 ` Len Brown
2008-05-15 1:55 ` Henrique de Moraes Holschuh [this message]
2008-05-14 11:36 ` Thomas Renninger
2008-05-14 11:42 ` Matthew Garrett
2008-05-14 12:49 ` Thomas Renninger
2008-05-14 12:56 ` Matthew Garrett
2008-05-14 15:28 ` 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=20080515015510.GD3415@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=avillaci@ceibo.fiec.espol.edu.ec \
--cc=cpufreq@lists.linux.org.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=patrol@sinus.cz \
/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