From: "Jim C. Brown" <jma5@umd.edu>
To: a_mulyadi@softhome.net, qemu-devel@nongnu.org
Subject: Re: Re: [Qemu-devel] Timing problems
Date: Sun, 28 Aug 2005 23:21:52 -0400 [thread overview]
Message-ID: <20050829032152.GA26595@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200508291001.39221.a_mulyadi@softhome.net>
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
> > intermittently, I hope, since the built in "virtual clock stop"
> > mechanism ist left unchanged.
>
> Hm..... hard choice.....correctness traded for perfomance.... But
> anyway....IMHO 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
>
The other patch for this just used a constant to increment the time iirc
(based on some value in /proc).
> BTW, your patch seems reversed....if you really mean you want to fetch
> realtime clock, you should use "rdtsc", right? But the patch seems
> replaced "rdtsc" with get_clock()....
>
The values returned by rdtsc seem to vary depending on cpu frequency when
speedstep is enabled. get_clock() is actually more accurate (tho i think less
precise), at least from the user land POV.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-08-29 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 19:23 [Qemu-devel] Timing problems Sven Zenker
2005-08-29 3:01 ` Mulyadi Santosa
2005-08-29 3:21 ` Jim C. Brown [this message]
2005-08-30 21:08 ` Sven Zenker
2005-08-31 12:19 ` Mulyadi Santosa
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=20050829032152.GA26595@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=a_mulyadi@softhome.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).