From: David Vrabel <david.vrabel@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel List <xen-devel@lists.xen.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, Tim Deegan <tim@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Migration memory corruption - PV backends need to quiesce
Date: Fri, 27 Jun 2014 18:28:08 +0100 [thread overview]
Message-ID: <53ADA9A8.6020103@citrix.com> (raw)
In-Reply-To: <53ADA10D.8030206@citrix.com>
On 27/06/14 17:51, Andrew Cooper wrote:
>
> Overall, it would appear that there needs to be a hook for all PV
> drivers to force quiescence. In particular, a backend must guarantee to
> unmap all active grant maps (so the frames get properly reflected in the
> dirty bitmap), and never process subsequent requests (so no new frames
> appear dirty in the bitmap after the guest has been paused).
I think this would be much too expensive for snapshots and things like
remus. Waiting for all outstanding I/O could take seconds.
David
next prev parent reply other threads:[~2014-06-27 17:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 16:51 Migration memory corruption - PV backends need to quiesce Andrew Cooper
2014-06-27 17:28 ` David Vrabel [this message]
2014-06-27 18:15 ` Tim Deegan
2014-06-27 18:37 ` Andrew Cooper
2014-06-30 8:38 ` Ian Campbell
2014-06-30 9:02 ` Andrew Cooper
2014-06-30 9:21 ` Ian Campbell
2014-06-30 9:46 ` Andrew Cooper
2014-06-30 9:52 ` Ian Campbell
2014-06-30 10:13 ` Andrew Cooper
2014-06-30 9:47 ` David Vrabel
2014-06-30 9:53 ` Ian Campbell
2014-07-01 10:29 ` David Vrabel
2014-07-02 10:02 ` Ian Campbell
2014-07-02 10:03 ` David Vrabel
2014-06-30 10:14 ` Tim Deegan
2014-06-30 10:24 ` Ian Campbell
2014-06-30 10:52 ` Tim Deegan
2014-06-30 11:07 ` Ian Campbell
2014-06-30 11:12 ` Tim Deegan
2014-06-30 11:57 ` David Vrabel
2014-06-30 12:20 ` Ian Campbell
2014-06-30 11:01 ` Ian Campbell
2014-06-30 11:08 ` Tim Deegan
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=53ADA9A8.6020103@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.