From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blueswir1@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] AIO and savevm
Date: Sun, 3 Sep 2006 11:49:15 +0100 [thread overview]
Message-ID: <200609031149.16112.paul@codesourcery.com> (raw)
In-Reply-To: <BAY104-F5A59D088CB3CECF26C6D4FF320@phx.gbl>
On Sunday 03 September 2006 11:42, Blue Swirl wrote:
> >When savevm is issued, you need to halt the guest CPUs, and wait for all
> > IO to
> >complete. While doing this you need to allow device AIO completion
> > routines to run, which may trigger additional IO. Once all IO has been
> > completed you should then be able to safely save state.
>
> How's this patch? Qemu_aio_poll waits for all AIOs and calls the device
> completion routines when each AIO finishes.
qemu_aio_poll doesn't wait. It returns immediately if IO has not completed
yet.
Paul
next prev parent reply other threads:[~2006-09-03 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 10:42 [Qemu-devel] AIO and savevm Blue Swirl
2006-09-03 10:49 ` Paul Brook [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-03 11:14 Blue Swirl
2006-09-03 12:08 ` Paul Brook
2006-09-02 15:28 Blue Swirl
2006-09-02 19:34 ` Paul Brook
2006-09-03 8:51 ` Blue Swirl
2006-09-03 10:23 ` 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=200609031149.16112.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blueswir1@hotmail.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).