From: clemens kurtenbach <moqua@kurtenba.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: cpufreq and p4 prescott
Date: Thu, 13 May 2004 11:19:30 +0200 [thread overview]
Message-ID: <40A33DA2.70708@kurtenba.ch> (raw)
In-Reply-To: <20040512171433.GA10481@dominikbrodowski.de>
Hi,
>>[ck@holodeck:cpufreq] cat /proc/cpuinfo | grep Mhz
>>cpu MHz : 2807.131
>>cpu MHz : 2807.131
>
> The cpu MHz entry in /proc/cpuinfo is the same for all CPUs, and no reliable
> source to detect the current cpu frequency anyway. Use
i thought this because on my ibook i can see different MHz
entry's when cpudyn changes the frequence.
> /sys/devices/system/cpu/cpu0/scaling_cur_freq or even cpuinfo_cur_freq for
> that.[*] So p4-clockmod-throttling does work on your p4 prescott.
>
> Dominik
>
> [*] Available in 2.6.7, hopefully, if Linus merges the latest cpufreq-bk
> tree from Dave. It'll be in the next -mm release, though.
o.k, when i understand you right p4-clockmod-throttling _is working_
on my system, but i can't see this in /sys until Dave Jones
patches are includet. So i patched my 2.6.6 kernel with
cpufreq-2004-05-13.diff.
Now cpuinfo_cur_freq and scaling_cur_freq show changing entry's
when eg powernowd handles the frequence.
The reason why i want to throttle down my prescott is the heat.
Strange is that when the frequence is changed to 350MHz
(after 30min running with 2.8GHz), neither the CPU&System temperature
nor tools that calculate the CPU speed (like gkrellm-x86info)
show a difference to 2.8GHz. All voltages on my system are the
same with 350MHz/2.8GHz, too.
So i'm not sure if throttling does work until now?
thanks,
clee
--
moqua [at] gmx.net
moqua [at] kurtenba.ch
next prev parent reply other threads:[~2004-05-13 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 17:14 Dominik Brodowski
2004-05-13 9:19 ` clemens kurtenbach [this message]
2004-05-13 15:30 ` rutger
2004-05-13 12:06 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 17:39 Dominik Brodowski
2004-05-14 21:47 ` rutger
2004-05-15 6:44 ` Dominik Brodowski
2004-05-15 10:52 ` rutger
2004-05-15 19:41 ` Dominik Brodowski
2004-05-16 13:20 ` Rutger Nijlunsing
2004-05-12 15:28 clemens kurtenbach
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=40A33DA2.70708@kurtenba.ch \
--to=moqua@kurtenba.ch \
--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
all inboxes | Powered by JetHome®