cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
* How does BIOS "thermal throttling" interact with cpufreq? (on VIA C7)
@ 2007-06-14 21:26 Phil Endecott
  2007-06-15 16:31 ` Wes Felter
  0 siblings, 1 reply; 2+ messages in thread
From: Phil Endecott @ 2007-06-14 21:26 UTC (permalink / raw)
  To: cpufreq

Dear Cpufreq experts,

I have a Jetway J7F2 motherboard with a VIA C7 processor and have 
recently got CPU frequency scaling working with the ondemand governor.  
It all works very smoothly - thanks.

In the BIOS settup screens there are options for "thermal throttling".  
They allow me to define a threshold voltage and a "duty cycle"; the 
screens are rather vague and there's nothing about it in the board 
documentation.  My guess is that when the CPU temperature reaches this 
threshold the clock speed is reduced.  I have looked at the datasheet 
for the chip that includes the temperature monitoring logic, and asked 
about it on the lm-sensors (aka hwmon) mailing list, and there seems to 
be an "over temp" output signal from this chip.  (The is also an 
"alarm" output, with a separate threshold register, which I think goes 
to the speaker.)

Does anyone know how this stuff works, and how it interacts with 
cpufreq?  Could it be that the "over temperature" signal is actually 
just an interrupt and software is supposed to respond by changing the 
frequency?  Does cpufreq need to be aware of this throttling function 
(i.e. having enabled cpufreq, have I unintentionally disabled this 
thermal protection?)

Any thoughts would be much appreciated.

Regards,

Phil.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: How does BIOS "thermal throttling" interact with cpufreq? (on VIA   C7)
  2007-06-14 21:26 How does BIOS "thermal throttling" interact with cpufreq? (on VIA C7) Phil Endecott
@ 2007-06-15 16:31 ` Wes Felter
  0 siblings, 0 replies; 2+ messages in thread
From: Wes Felter @ 2007-06-15 16:31 UTC (permalink / raw)
  To: cpufreq

Phil Endecott wrote:
> Dear Cpufreq experts,
> 
> I have a Jetway J7F2 motherboard with a VIA C7 processor and have 
> recently got CPU frequency scaling working with the ondemand governor.  
> It all works very smoothly - thanks.
> 
> In the BIOS settup screens there are options for "thermal throttling".  
> They allow me to define a threshold voltage and a "duty cycle"; the 
> screens are rather vague and there's nothing about it in the board 
> documentation.  My guess is that when the CPU temperature reaches this 
> threshold the clock speed is reduced.  I have looked at the datasheet 
> for the chip that includes the temperature monitoring logic, and asked 
> about it on the lm-sensors (aka hwmon) mailing list, and there seems to 
> be an "over temp" output signal from this chip.  (The is also an "alarm" 
> output, with a separate threshold register, which I think goes to the 
> speaker.)
> 
> Does anyone know how this stuff works, and how it interacts with 
> cpufreq?  Could it be that the "over temperature" signal is actually 
> just an interrupt and software is supposed to respond by changing the 
> frequency?  Does cpufreq need to be aware of this throttling function 
> (i.e. having enabled cpufreq, have I unintentionally disabled this 
> thermal protection?)

If they've done it really right (like Intel TM1/TM2), then the CPU will 
handle everything transparently for you. If they've done it right, then 
overtemp will trigger a system management interrupt (SMI) and BIOS code 
will set the IA32_CLOCK_MODULATION register; because clock modulation is 
(supposed to be) orthogonal to EIST it should work fine. If they do it 
some other way then who knows.

Wes Felter - wesley@felter.org

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-06-15 16:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-14 21:26 How does BIOS "thermal throttling" interact with cpufreq? (on VIA C7) Phil Endecott
2007-06-15 16:31 ` Wes Felter

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox