Hello Sven...
> rdtsc gives you the cpu's clock count, which, if CPU frequency
> changes, or your code is run on different processors (multiprocessor
> machine), cannot be assumed to be related to real time anymore.
> Resolutionwise, the real time clock may be inferior, of course, as
> Jim mention
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
On Mon, Aug 29, 2005 at 10:01:39AM +0700, Mulyadi Santosa wrote:
> Hello...
>
> > It simply
> > replaces the virtual timer mechanism based on CPU tick count (which
> > is totally messed up in a SpeedStep setting) with calls to the
> > realtime clock. It should work even when emulation is stopped
>
Hello...
> It simply
> replaces the virtual timer mechanism based on CPU tick count (which
> is totally messed up in a SpeedStep setting) with calls to the
> realtime clock. It should work even when emulation is stopped
> intermittently, I hope, since the built in "virtual clock stop"
> mechanism
Hi all,
as a new qemu user, let me first of all say that qemu, especially in
combination with kqemu is a great piece of software. Many thanks to the
developer(s).
Since I am using a Laptop with a Pentium M CPU with SpeedStep and am
forced to use XP SP2 as a guest OS (Suse 9.3 is host OS), it wouldn
Oliver Gerlich wrote:
> Alexander Toresson wrote:
> > I'm running windows 2000 in qemu 0.7.0 with kqemu 0.6.2-1 on i386
> > debian linux. First thing I tried to do was to run a benchmark program
> > (qemu w/o kqemu vs qemu w/ kqemu). I got strange results, and I also
> > noted that timing didn't se
On Wed, 29 Jun 2005, Alexander Toresson wrote:
I'm running windows 2000 in qemu 0.7.0 with kqemu 0.6.2-1 on i386
debian linux. First thing I tried to do was to run a benchmark program
(qemu w/o kqemu vs qemu w/ kqemu). I got strange results, and I also
noted that timing didn't seem to be that go
Alexander Toresson wrote:
I'm running windows 2000 in qemu 0.7.0 with kqemu 0.6.2-1 on i386
debian linux. First thing I tried to do was to run a benchmark program
(qemu w/o kqemu vs qemu w/ kqemu). I got strange results, and I also
noted that timing didn't seem to be that good, so I re-tried to r
