From: Thomas Renninger <trenn@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Len Brown" <lenb@kernel.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 13:36:14 +0200 [thread overview]
Message-ID: <1210764974.29724.181.camel@queen.suse.de> (raw)
In-Reply-To: <20080514005636.GA21608@srcf.ucam.org>
On Wed, 2008-05-14 at 01:56 +0100, Matthew Garrett wrote:
> On Tue, May 13, 2008 at 08:48:00PM -0400, Len Brown wrote:
>
> > Assuming this is a laptop with a batter,
> > I'd certainly be interested if you could run BLTK
> > and measure any benefit to p4-clockmod (I've never
> > been able to)
>
> The most plausible benefit to p4-clockmod is its utility in throttling
> the CPU if it would otherwise cause the system to overheat. From that
> point of view, I think it's worth keeping around - especially since not
> all machines expose T states via ACPI.
If you think it's worth it..., but it needs a new implementation (at
another place). So just removing it for now should be best to avoid
further confusion.
Also there is another interface via mce:
arch/x86/kernel/cpu/mcheck/therm_throt.c
AFAIK this should be implemented in (all?) P4s, but Intel people should
know for sure.
This one should kick in for sure on high temperatures, are there any P4s
with a passive trip point defined?
I like the idea of reimplementing this via throttling interface. But
this is more for calming P4 users conscience (I saw my P4 running at 300
MHz on Windows) than for any real use.
Thomas
next prev parent reply other threads:[~2008-05-14 11:36 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
2008-05-14 11:36 ` Thomas Renninger [this message]
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=1210764974.29724.181.camel@queen.suse.de \
--to=trenn@suse.de \
--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 \
/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