From: "Benoît Canet" <benoit.canet@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com,
"Benoît Canet" <benoit.canet@gmail.com>,
stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH V2 0/7] Make QED with live migration safe
Date: Wed, 21 Mar 2012 16:51:57 +0100 [thread overview]
Message-ID: <1332345124-381-1-git-send-email-benoit.canet@gmail.com> (raw)
This is the second version of a patchset aiming at making the combined
usage of QED and live migration safe.
Since v1:
-The block layer is not aware anymore of the migration state. (stefanha)
-No bdrv_invalidate_cache renaming since the semantic do not change. (stefanha)
-The qed bdrv_invalidate_cache function does a reopening of the image to flush
metadata and to do the image integrity check. (stefanha)
note:
In "qed: honor BDRV_O_INCOMING for incoming live migration" I choose to
honor bs->open_flags and not s->flags in order to keep the
bdrv_qed_invalidate_cache function intact of any migration related operation.
This way bdrv_qed_invalidate_cache semantic is not changed.
Benoît Canet (7):
block: Add new BDRV_O_INCOMING flag to notice incoming live migration
block: add a function to clear incoming live migration flags
blockdev: open images with BDRV_O_INCOMING on incoming live migration
qed: add bdrv_invalidate_cache to be called after incoming live
migration
migration: clear BDRV_O_INCOMING flags on end of incoming live
migration
qed: honor BDRV_O_INCOMING for incoming live migration
qed: remove incoming live migration blocker
block.c | 9 +++++++++
block.h | 3 +++
block/qed.c | 29 ++++++++++++++++++-----------
block/qed.h | 3 +--
blockdev.c | 4 ++++
migration.c | 1 +
6 files changed, 36 insertions(+), 13 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-03-21 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:51 Benoît Canet [this message]
2012-03-21 15:51 ` [Qemu-devel] [PATCH V2 1/7] block: Add new BDRV_O_INCOMING flag to notice incoming live migration Benoît Canet
2012-03-21 15:51 ` [Qemu-devel] [PATCH V2 2/7] block: add a function to clear incoming live migration flags Benoît Canet
2012-03-21 15:52 ` [Qemu-devel] [PATCH V2 3/7] blockdev: open images with BDRV_O_INCOMING on incoming live migration Benoît Canet
2012-03-21 15:52 ` [Qemu-devel] [PATCH V2 4/7] qed: add bdrv_invalidate_cache to be called after " Benoît Canet
2012-03-22 13:21 ` Stefan Hajnoczi
2012-03-22 14:15 ` Benoît Canet
2012-03-22 14:17 ` Paolo Bonzini
2012-03-22 15:30 ` Stefan Hajnoczi
2012-03-21 15:52 ` [Qemu-devel] [PATCH V2 5/7] migration: clear BDRV_O_INCOMING flags on end of " Benoît Canet
2012-03-21 15:52 ` [Qemu-devel] [PATCH V2 6/7] qed: honor BDRV_O_INCOMING for " Benoît Canet
2012-03-21 15:52 ` [Qemu-devel] [PATCH V2 7/7] qed: remove incoming live migration blocker Benoît Canet
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=1332345124-381-1-git-send-email-benoit.canet@gmail.com \
--to=benoit.canet@gmail.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).