From: Thanasis <thanasis@asyr.hopto.org>
To: gentoo-amd64@lists.gentoo.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [gentoo-amd64] Is /proc/cpuinfo showing the actual frequency ?
Date: Thu, 19 Feb 2009 21:05:32 +0200 [thread overview]
Message-ID: <499DAD7C.4060404@asyr.hopto.org> (raw)
In-Reply-To: <58965d8a0902190946k3f0be02nd3f4eef4827cc08a@mail.gmail.com>
on 02/19/2009 07:46 PM Paul Hartman wrote the following:
> On Thu, Feb 19, 2009 at 10:55 AM, Justin <justin@j-schmitz.net> wrote:
>> Thanasis schrieb:
>>> on 02/19/2009 06:23 PM Justin wrote the following:
>>>> Thanasis schrieb:
>>>>
>>>>> # uname -a
>>>>> Linux wolfdale 2.6.28-gentoo-r2 #1 SMP PREEMPT Wed Feb 18 13:53:22 EET
>>>>> 2009 x86_64 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel
>>>>> GNU/Linux
>>>>>
>>>>> Overclocked the core 2 duo (E8400) from 3 to 4GHz using motherboard
>>>>> BIOS settings. In mswindblows I can see the overclocked frequency
>>>>> (when cpu is under load), in linux /proc/cpuinfo never shows beyond the
>>>>> stock 3GHz value.
>>>>>
>>>>> Q: Is /proc/cpuinfo showing the actual frequency?
>>>>>
>>>>>
>>>> Do you have frequency scaling active?
>>> Yes, but the /proc/cpuinfo I showed, was with the max frequency ever
>>> displayed (under load).
>>>
>> AFAIK the scaling will interfere with OC. Try to disable it and check
>> again.
>
> I just did some googling and it seems that frequency scaling in linux
> only works with the stock speed steps, not the OC'ed speed.
I bet if I disable frequency scaling from BIOS, it will show 4GHz, because the
funny thing is that inside a fully VM (guest) it shows the "real" frequency ;-)
# cat cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
stepping : 10
cpu MHz : 4050.236
cache size : 6144 KB
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
clflush dts mmx fxsr sse sse2 ss syscall nx lm pni ds_cpl cx16 xtpr lahf_lm
bogomips : 8111.05
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
stepping : 10
cpu MHz : 4050.236
cache size : 6144 KB
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
clflush dts mmx fxsr sse sse2 ss syscall nx lm pni ds_cpl cx16 xtpr lahf_lm
bogomips : 8101.80
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
parent reply other threads:[~2009-02-19 19:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <58965d8a0902190946k3f0be02nd3f4eef4827cc08a@mail.gmail.com>]
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=499DAD7C.4060404@asyr.hopto.org \
--to=thanasis@asyr.hopto.org \
--cc=gentoo-amd64@lists.gentoo.org \
--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®