Hi,
people have had this problem with SpeedStep machines, where it is
related to qemu timing being based on CPU cycle count, which is thereby
messed up.
Since it seems to occur with frequency scaling disabled as well, could
this be related to running on a HyperThreading CPU? Not sure what
happens
Had the same problem on my SpeedStep machine, am using an ugly patch
currently that replaces the CPU tick based timing with calls to the
realtime clock (see my previous mails on this list). Runs XP as guest
quite reliably under Suse 9.3 (using it every day to run Windows only
software). Performance
Hi,
> Hm. hard choice.correctness traded for perfomance But
> anywayIMHO this hack is needed for every speed-step enabled
> machine. Perhaps...the other workaround is via cpufreqd? I don't have
> any Pentium M based PC/laptop around, so this is just a pure guess
Yeah, you can al
clock();
return get_clock();
---
> return val;
++
This is of course an ugly hack and sure to affect performance, but at
least, it makes XP work for me.
Please let me know your thoughts.
Best regards,
Sven Zenker
--
Dr. med. Sven Zenker
Res
