From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Len Brown <lenb@kernel.org>
Cc: 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: Thu, 15 May 2008 00:11:29 +0100 [thread overview]
Message-ID: <20080514231129.GB11960@srcf.ucam.org> (raw)
In-Reply-To: <200805141118.38324.lenb@kernel.org>
On Wed, May 14, 2008 at 11:18:37AM -0400, Len Brown wrote:
> On Wednesday 14 May 2008, Matthew Garrett wrote:
> > Check processor_thermal.c. It explicitly interfaces with cpufreq in
> > order to perform P state management.
>
> The hook above is so that ACPI thermal throttling
> does not invoke T-states until the more efficient
> P-states have already been exhausted.
>
> It doesn't imply the presence of thermal awareness
> anywhere in the cpufreq sub-system.
The cpufreq sub-system itself isn't aware of thermal issues, but the
ACPI system is. I'm not sure that the distinction's especially
important.
> It also doesn't imply that running cpufreq on top
> of T-states is a good idea. Cpufreq as implemented,
> say by the ondemand governor, is based
> on the assumption that it is running on top of
> P-states. Deeper P-states result in
> more efficient operation (less energy/instruction)
> due to their lower voltage, because energy varies with voltage^2.
> T-states violate that assumpion and provide
> all the performance cost with none of the efficiency
> gains of P-states, because energy varies directly
> with frequencey -- but so does performance cost.
Right. I'm not implying that this is a desirable situation, but the fact
remains that some machines will reach critical shutdown temperature
unless something is done to reduce the speed of the processor. If you
don't have P states or ACPI-exposed T states, then p4-clockmod is about
the best you can manage.
> > > There is already a well known thermal throttling interface
> > > available via ACPI and it does not need p4_clockmod to run.
> > > Passive trip points work automatically even without cpufreq being present.
> > > If they do not, then we need to fix them.
> >
> > You're assuming that the throttling interface is always exposed via
> > ACPI. I've seen machines where this isn't the case.
>
> Please show me those machines.
http://www.google.co.uk/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=R8P&q=acpi+throttling+"<not+supported>"+-C3&btnG=Search&meta=
(a lot of false positives, but many of these are genuine)
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-05-14 23:11 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 [this message]
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
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=20080514231129.GB11960@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=avillaci@ceibo.fiec.espol.edu.ec \
--cc=cpufreq@lists.linux.org.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.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