cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: cpufreq@www.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Tue, 21 Oct 2003 13:09:16 +0200	[thread overview]
Message-ID: <yw1x3cdmetk3.fsf@kth.se> (raw)
In-Reply-To: yw1xbrsaeu44.fsf@kth.se

mru@kth.se (Måns Rullgård) writes:

>> Most of the latest CPUs (laptop CPUs in particular) have feature 
>> which enable very low latency P-state transitions 
>> (like Enhanced Speedstep Technology-EST). Using this feature, 
>> we can have a lightweight in kernel cpufreq governor, 
>> to vary CPU frequency depending on the CPU usage. The 
>> advantage being low power consumption and also cooler laptops.
>
> So, I took this thing for a spin, but it didn't work at all.  I loaded
> the module, and did "echo demandbased > /sys/.../scaling_governor".
> This echo never returned, and the keyboard locked up.  After a little
> while, the fan started running at full speed.  I managed to cut and
> paste into an xterm and start top, which showed nothing unusual.  I
> could shut down and reboot normally.

I might add that this was on an Asus M2400E laptop.

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 2
model name	: Mobile Intel(R) Pentium(R) 4 - M CPU 1.80GHz
stepping	: 7
cpu MHz		: 2070.179
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips	: 4087.80

-- 
Måns Rullgård
mru@kth.se

  reply	other threads:[~2003-10-21 11:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  2:56 [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver Pallipadi, Venkatesh
2003-10-21  8:25 ` Måns Rullgård
2003-10-21 20:47   ` Dominik Brodowski
2003-10-21 10:57 ` Måns Rullgård
2003-10-21 11:09   ` Måns Rullgård [this message]
2003-10-21 20:30   ` Alexander Bokovoy
2003-10-21 20:39     ` Måns Rullgård
2003-10-21 21:11       ` Alexander Bokovoy
2003-10-21 21:37         ` Måns Rullgård
2003-10-21 21:53           ` Alexander Bokovoy
2003-10-21 22:27             ` Måns Rullgård
  -- strict thread matches above, loose matches on Subject: below --
2003-10-22  1:42 Pallipadi, Venkatesh
2003-10-22  1:48 Pallipadi, Venkatesh
2003-10-22 18:21 Pallipadi, Venkatesh
2003-10-23  8:19 ` Arjan van de Ven
2003-10-23  8:24   ` Alexander Bokovoy
2003-10-23  8:29     ` Arjan van de Ven
2003-10-23 18:03       ` Ducrot Bruno
2003-10-23 18:16   ` Todd Poynor
2003-10-23 18:26     ` Todd Poynor
2003-11-02 20:28 ` Jan Rychter
2003-11-04  3:14 Brown, Len
2003-11-04  3:21 ` Jan Rychter
2003-11-04  7:16   ` Dominik Brodowski
2003-11-05 21:12 Mukesh Rajan

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=yw1x3cdmetk3.fsf@kth.se \
    --to=mru@kth.se \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@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