From: Anthony PERARD <anthony.perard@citrix.com>
To: QEMU-devel <qemu-devel@nongnu.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Xen Devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Avi Kivity <avi@redhat.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] [PATCH V2 5/5] xen: Always set the vram dirty during migration.
Date: Fri, 20 Jul 2012 15:34:42 +0100 [thread overview]
Message-ID: <1342794882-30648-6-git-send-email-anthony.perard@citrix.com> (raw)
In-Reply-To: <1342794882-30648-1-git-send-email-anthony.perard@citrix.com>
Because the call to track the dirty bit in the video ram during migration won't
work (it returns -1), we set dirtybit on the all video ram.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
xen-all.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/xen-all.c b/xen-all.c
index 54e54cb..207182e 100644
--- a/xen-all.c
+++ b/xen-all.c
@@ -502,6 +502,11 @@ static void xen_sync_dirty_bitmap(XenIOState *state,
return;
}
+ if (unlikely(xen_in_migration)) {
+ /* track_dirty_vram does not work during migration */
+ memory_region_set_dirty(framebuffer, 0, size);
+ return;
+ }
rc = xc_hvm_track_dirty_vram(xen_xc, xen_domid,
start_addr >> TARGET_PAGE_BITS, npages,
bitmap);
--
Anthony PERARD
prev parent reply other threads:[~2012-07-20 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 14:34 [Qemu-devel] [PATCH V2 0/5] Xen, introducing dirty log for migration Anthony PERARD
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 1/5] QMP, Introduce xen-set-global-dirty-log command Anthony PERARD
2012-07-27 16:30 ` Luiz Capitulino
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 2/5] xen: Introduce xen_modified_memory Anthony PERARD
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 3/5] exec: Introduce helper to set dirty flags Anthony PERARD
2012-07-29 12:58 ` Avi Kivity
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 4/5] exec, memory: Call to xen_modified_memory Anthony PERARD
2012-07-20 14:34 ` Anthony PERARD [this message]
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=1342794882-30648-6-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@citrix.com \
--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 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).