$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 12
model name : AMD Athlon(tm) 64 Processor 3000+
stepping : 0
cpu MHz : 0.000
cache size : 512 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 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm
bogomips : 811.00
" cpu MHz : 0.000 "
The cpu clock detected incorrect from cpuid, is it normal in colinux?
because this may make some program failure to run.
but there is correct from kernel.
$ uname -a
Linux colinux 188.8.131.52-co-0.6.2-pre4 #1 Fri Oct 8 19:03:25 HKT 2004
i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
From: Nuno Lucas <lucas@nl...> - 2004-10-08 18:40:52
Paradise, dando pulos de alegria, escreveu :
> " cpu MHz : 0.000 "
> The cpu clock detected incorrect from cpuid, is it normal in colinux?
> because this may make some program failure to run.
It is normal. I believe UML does the same thing.
It is possible some programs fail to run properly witout this, but I
would also add that any program depending on this info is a very broken
> but there is correct from kernel.
> $ uname -a
> Linux colinux 184.108.40.206-co-0.6.2-pre4 #1 Fri Oct 8 19:03:25 HKT 2004
> i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
The text you see is the cpu name as given by the CPUID functionallity.
To find the "real" CPU frequency, we need special code that is disabled
now, as it would(could?) crash the windows machine.
I didn't looked at that code, but it's the only (and very strong) reason
I can envision for not using it, as the Linux kernel thinks he has total
control of the machine at the time doing the test.
It would not be too hard to implement it, but I don't see any reason to
do it at this time.
Get latest updates about Open Source Projects, Conferences and News.