All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] WinXp Guest clock drift
Date: Tue, 22 Mar 2005 09:28:33 +0100	[thread overview]
Message-ID: <aec7e5c305032200283b735992@mail.gmail.com> (raw)
In-Reply-To: <423FD59B.9050808@wasp.net.au>

On Tue, 22 Mar 2005 12:21:47 +0400, Brad Campbell <brad@wasp.net.au> wrote:
> Magnus Damm wrote:
> > On Mon, 21 Mar 2005 23:15:24 -0800, Mike Swanson
> > <mikeonthecomputer@gmail.com> wrote:
> >
> >>Well, this is probably a nuisance in all emulators :p
> >
> >
> > Does it have to be that way? I mean - if a media player can keep track
> > of the time of a movie (with and without sound) then wouldn't it be
> > possible for other applications like emulators to keep accurate time?
> >
> > I do not know how the time is handled in QEMU, but I wrote code some
> > years ago that monitored itself with gettimeofday() and adjusted the
> > drift on the fly.
> 
> I actually find all sorts of oddities with timing and qemu emulation. Sometimes when installing
> stuff in a windows guest the guest slows to a crawl until I move the mouse around or drag a window
> or something similar. Almost like it starts to go to sleep until it gets some user interaction.

I second that observation.

> There are a number of emulation oddities thus far, I just get used to them and work around them. I
> guess I should actually have a go at debugging them really.

The same goes for me...

/ magnus

  reply	other threads:[~2005-03-22  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22  6:12 [Qemu-devel] WinXp Guest clock drift Brad Campbell
2005-03-22  7:15 ` Mike Swanson
2005-03-22  8:13   ` Magnus Damm
2005-03-22  8:21     ` Brad Campbell
2005-03-22  8:28       ` Magnus Damm [this message]
2005-03-22  8:53       ` John R. Hogerhuis
2005-03-22  8:17   ` Brad Campbell

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=aec7e5c305032200283b735992@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.