| 1 |
Martin Herrman schrieb: |
| 2 |
> |
| 3 |
> |
| 4 |
> 2009/2/19 Thanasis <thanasis@××××××××××.org |
| 5 |
> <mailto:thanasis@××××××××××.org>> |
| 6 |
> |
| 7 |
> # uname -a |
| 8 |
> Linux wolfdale 2.6.28-gentoo-r2 #1 SMP PREEMPT Wed Feb 18 13:53:22 EET |
| 9 |
> 2009 x86_64 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel |
| 10 |
> GNU/Linux |
| 11 |
> |
| 12 |
> Overclocked the core 2 duo (E8400) from 3 to 4GHz using motherboard |
| 13 |
> BIOS settings. In mswindblows I can see the overclocked frequency |
| 14 |
> (when cpu is under load), in linux /proc/cpuinfo never shows beyond the |
| 15 |
> stock 3GHz value. |
| 16 |
> |
| 17 |
> Q: Is /proc/cpuinfo showing the actual frequency? |
| 18 |
> |
| 19 |
> # cat cpuinfo |
| 20 |
> processor : 0 |
| 21 |
> vendor_id : GenuineIntel |
| 22 |
> cpu family : 6 |
| 23 |
> model : 23 |
| 24 |
> model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz |
| 25 |
> stepping : 10 |
| 26 |
> cpu MHz : 2997.000 |
| 27 |
> cache size : 6144 KB |
| 28 |
> physical id : 0 |
| 29 |
> siblings : 2 |
| 30 |
> core id : 0 |
| 31 |
> cpu cores : 2 |
| 32 |
> apicid : 0 |
| 33 |
> initial apicid : 0 |
| 34 |
> fpu : yes |
| 35 |
> fpu_exception : yes |
| 36 |
> cpuid level : 13 |
| 37 |
> wp : yes |
| 38 |
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr |
| 39 |
> pge mca cmov |
| 40 |
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm |
| 41 |
> constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl |
| 42 |
> vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow |
| 43 |
> vnmi flexpriority |
| 44 |
> bogomips : 8099.96 |
| 45 |
> clflush size : 64 |
| 46 |
> cache_alignment : 64 |
| 47 |
> address sizes : 36 bits physical, 48 bits virtual |
| 48 |
> power management: |
| 49 |
> |
| 50 |
> processor : 1 |
| 51 |
> vendor_id : GenuineIntel |
| 52 |
> cpu family : 6 |
| 53 |
> model : 23 |
| 54 |
> model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz |
| 55 |
> stepping : 10 |
| 56 |
> cpu MHz : 2997.000 |
| 57 |
> cache size : 6144 KB |
| 58 |
> physical id : 0 |
| 59 |
> siblings : 2 |
| 60 |
> core id : 1 |
| 61 |
> cpu cores : 2 |
| 62 |
> apicid : 1 |
| 63 |
> initial apicid : 1 |
| 64 |
> fpu : yes |
| 65 |
> fpu_exception : yes |
| 66 |
> cpuid level : 13 |
| 67 |
> wp : yes |
| 68 |
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr |
| 69 |
> pge mca cmov |
| 70 |
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm |
| 71 |
> constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl |
| 72 |
> vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow |
| 73 |
> vnmi flexpriority |
| 74 |
> bogomips : 8099.74 |
| 75 |
> clflush size : 64 |
| 76 |
> cache_alignment : 64 |
| 77 |
> address sizes : 36 bits physical, 48 bits virtual |
| 78 |
> power management: |
| 79 |
> |
| 80 |
> |
| 81 |
> I have noticed exactly the same while overclocking my Q9300 from it's |
| 82 |
> stock 2.5 GHZ to 3.2 GHZ. Compilation / encode transactions do take much |
| 83 |
> less time, so I assume that the BIOS information is correct and the |
| 84 |
> /proc/ entry is false. |
| 85 |
|
| 86 |
If you downstep your cpu it is shown: |
| 87 |
|
| 88 |
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz |
| 89 |
stepping : 11 |
| 90 |
cpu MHz : 1600.000 |
| 91 |
|
| 92 |
But perhaps it just read the step and knows which frequency belongs to that. |
Archives