From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Timers
Date: Wed, 23 May 2007 22:56:39 +0100 [thread overview]
Message-ID: <200705232256.40404.paul@codesourcery.com> (raw)
In-Reply-To: <fb249edb0705231353n1e101326lc6d9323574442736@mail.gmail.com>
> > Code looks reasonable to me. The FIXME means you're changing the timer
> > parameters after starting the timer. I didn't check whether this does
> > anything sensible (this may depend on the device), hence the message.
> > It probably needs some attention when reload == 1 && s->enabled.
> >
> > Note that save/restore is not implemented. You may wish to implement
> > this
>
> I was thinking that it should be possible to save/restore all vm_clock
> based timers in qemu at QEMUTimer level so that hardware emulation
> doesn't have to bother restoring this. (the "ptimer" would still need
> to save its internal fields).
The problem is that the timer itself doesn't know which device it is attached
to. There's no way to ensure that the state is loaded into the correct
timers. Remember that qemu can be restarted (and all timers reallocated) in
between the save and the load.
There are already qemu_put_timer and qemu_get_timer routines.
I notice that the existing slavio_timer_{save,load} don't use these, so are
probably already broken.
Paul
next prev parent reply other threads:[~2007-05-23 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 0:06 [Qemu-devel] Timers Paul Brook
2007-05-23 0:52 ` George G. Davis
2007-05-23 1:14 ` Paul Brook
2007-05-23 1:39 ` George G. Davis
2007-05-23 17:00 ` Blue Swirl
2007-05-23 17:18 ` Paul Brook
2007-05-23 19:28 ` Blue Swirl
2007-05-23 19:48 ` Paul Brook
2007-05-23 20:53 ` andrzej zaborowski
2007-05-23 21:56 ` Paul Brook [this message]
2007-05-24 19:18 ` Blue Swirl
2007-05-24 19:28 ` Paul Brook
2007-05-23 17:25 ` George G. Davis
2007-05-23 17:58 ` Paul Brook
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=200705232256.40404.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@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 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).