Re: constant processor 0x80 events

Faye Pearson
2003-01-02T13:59:37Z

Faye Pearson [faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org] wrote:
> I've used THRT as the one shot flag in the meantime and I'll see how it
> goes.

> > eg. in _L00
> >
> > If (LNot(THRT)) {
> > Store (One, THRT)
> > Notify (\_PR.CPU0, 0x80)
> > }
> >
> > and in _PPC
> >
> > If (THRT) {
> > Store (Zero, THRT)
> > Return (One)
> > }

This has (almost) the desired (or at least helpful) effect.

Used in combination with the autospeedstep daemon, once this threshold
has been met:

root@marmite faye # cat /proc/acpi/processor/CPU0/performance
state count: 2
active state: P1
states:
P0: 1200 MHz, 20000 mW, 250 uS
*P1: 800 MHz, 10000 mW, 250 uS

The processor is switched to low power mode and autospeedstep didn't do
it:

root@marmite faye # tail /var/log/speedstep
Thu Jan 2 13:23:44 2003: max. speed mode
Thu Jan 2 13:24:01 2003: power save mode
Thu Jan 2 13:24:12 2003: max. speed mode
Thu Jan 2 13:31:19 2003: power save mode
Thu Jan 2 13:37:03 2003: max. speed mode

It still thinks it's in max. speed mode.

root@marmite faye # cat /proc/acpi/thermal_zone/THRM/temperature
temperature: 51 C

The processor is now relatively chilled, it would be nice if it would
try to trip up again, but that's for me to change in autospeedstep.

> This is what I'm currently running with. The thing is I'm not sure
> whether that will cause any other side effects - any ideas?

Still not sure about the side effects.

Faye

--
Faye Pearson,
Covert Development
ClaraNET Ltd. Tel 020 7903 3000

I am the mother of all things, and all things should wear a sweater.