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
