From: "Mark W. Alexander" <slash@dotnetslash.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.0->2.6.1 /proc/cpuinfo behavior change
Date: Sun, 11 Jan 2004 14:28:29 -0500 [thread overview]
Message-ID: <20040111192829.GA27147@dotnetslash.net> (raw)
I'm not currently subscribed. Please cc: me on responses.
The behavior of /proc/cpuinfo on cpu frequency scaling has changed
between 2.6.0 and 2.6.1(-mm2). On 2.6.0, /proc/cpuinfo reports the cpu
MHz as set by scaling_setspeed, with bogo-mips numbers along traditional
values.
On 2.6.1-mm2, /proc/cpuinfo _always_ reports cpu MHz == cpuinfo_max_freq, with
bogo-mips values closer to the setting of scaling_setspeed.
In both cases, /proc/stat information appears appropriate to the actual
speed. (At least, AFAICT, that's where gKrellm get's it's info and it seems
to report correctly.)
I didn't glean anything from the changelogs that explains this behavior. Is
it a bug or a feature?
Example output:
########################### 2.6.0 ######################
bash-2.05b# uname -r
2.6.0-ze4400-3
bash-2.05b# echo 1800000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
bash-2.05b# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : mobile AMD Athlon(tm) XP2200+
stepping : 1
cpu MHz : 1788.655
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips : 3538.94
bash-2.05b# echo 532000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
bash-2.05b# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : mobile AMD Athlon(tm) XP2200+
stepping : 1
cpu MHz : 529.971
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips : 1048.57
########################### 2.6.1-mm2 ######################
bash-2.05b# uname -r
2.6.1-mm2-ze4400-1
bash-2.05b# echo 1800000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
bash-2.05b# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : mobile AMD Athlon(tm) XP2200+
stepping : 1
cpu MHz : 1789.000
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips : 1777.66
bash-2.05b# echo 532000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
bash-2.05b# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : mobile AMD Athlon(tm) XP2200+
stepping : 1
cpu MHz : 1789.000
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips : 526.71
--
Mark W. Alexander
slash@dotnetslash.net
reply other threads:[~2004-01-11 19:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040111192829.GA27147@dotnetslash.net \
--to=slash@dotnetslash.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.