public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
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 14:49:18 +0200	[thread overview]
Message-ID: <1210769358.21269.21.camel@queen.suse.de> (raw)
In-Reply-To: <20080514114215.GA31135@srcf.ucam.org>

On Wed, 2008-05-14 at 12:42 +0100, Matthew Garrett wrote:
> On Wed, May 14, 2008 at 01:36:14PM +0200, Thomas Renninger wrote:
> 
> > 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.
> 
> Hm. The MCE interface is only for reporting, rather than control. Do you 
> know if it's possible to set the temperature at which the CPU will start 
> its own throttling? That would potentially be more straightforward.

AFAIK there is not much to control from OS side.
All you get is an event, or better an exception, that BIOS detected too
high temperatures on the CPU and that your CPU is currently not running
at full speed.
The p4 parts seem to sit here:
arch/x86/kernel/cpu/mcheck/p4.c

You might find a hack to modify this, by reading P4 (this seem to sit in
the CPU itself?) or chipset specs. But again, is it worth it for a P4
where no power saving capabilities are present anyway?

  Thomas


  reply	other threads:[~2008-05-14 12:49 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
2008-05-14 11:42       ` Matthew Garrett
2008-05-14 12:49         ` Thomas Renninger [this message]
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=1210769358.21269.21.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