From: Jeff Cody <jcody@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 3/4] migration/block: Clean up BBs in block_save_complete()
Date: Tue, 30 May 2017 11:32:56 -0400 [thread overview]
Message-ID: <20170530153256.GC2665@localhost.localdomain> (raw)
In-Reply-To: <1496157773-10779-4-git-send-email-kwolf@redhat.com>
On Tue, May 30, 2017 at 05:22:52PM +0200, Kevin Wolf wrote:
> We need to release any block migrations BlockBackends on the source
> before successfully completing the migration because otherwise
> inactivating the images will fail (inactivation only tolerates device
> BBs).
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> Reviewed-by: Fam Zheng <famz@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> migration/block.c | 22 +++++++++++++++++-----
> 1 file changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/migration/block.c b/migration/block.c
> index 13f90d3..deb4b0e 100644
> --- a/migration/block.c
> +++ b/migration/block.c
> @@ -673,16 +673,14 @@ static int64_t get_remaining_dirty(void)
> return dirty << BDRV_SECTOR_BITS;
> }
>
> -/* Called with iothread lock taken. */
>
> -static void block_migration_cleanup(void *opaque)
> +
> +/* Called with iothread lock taken. */
> +static void block_migration_cleanup_bmds(void)
> {
> BlkMigDevState *bmds;
> - BlkMigBlock *blk;
> AioContext *ctx;
>
> - bdrv_drain_all();
> -
> unset_dirty_tracking();
>
> while ((bmds = QSIMPLEQ_FIRST(&block_mig_state.bmds_list)) != NULL) {
> @@ -700,6 +698,16 @@ static void block_migration_cleanup(void *opaque)
> g_free(bmds->aio_bitmap);
> g_free(bmds);
> }
> +}
> +
> +/* Called with iothread lock taken. */
> +static void block_migration_cleanup(void *opaque)
> +{
> + BlkMigBlock *blk;
> +
> + bdrv_drain_all();
> +
> + block_migration_cleanup_bmds();
>
> blk_mig_lock();
> while ((blk = QSIMPLEQ_FIRST(&block_mig_state.blk_list)) != NULL) {
> @@ -843,6 +851,10 @@ static int block_save_complete(QEMUFile *f, void *opaque)
>
> qemu_put_be64(f, BLK_MIG_FLAG_EOS);
>
> + /* Make sure that our BlockBackends are gone, so that the block driver
> + * nodes can be inactivated. */
> + block_migration_cleanup_bmds();
> +
> return 0;
> }
>
> --
> 1.8.3.1
>
>
Reviewed-by: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2017-05-30 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 15:22 [Qemu-devel] [PATCH v2 0/4] Block migration (migrate -b) fixes Kevin Wolf
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 1/4] block: Fix anonymous BBs in blk_root_inactivate() Kevin Wolf
2017-05-30 15:28 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 2/4] migration: Inactivate images after .save_live_complete_precopy() Kevin Wolf
2017-05-30 15:29 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 3/4] migration/block: Clean up BBs in block_save_complete() Kevin Wolf
2017-05-30 15:32 ` Jeff Cody [this message]
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 4/4] qemu-iotests: Block migration test Kevin Wolf
2017-05-30 15:52 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 16:57 ` Kevin Wolf
2017-05-30 18:48 ` Jeff Cody
2017-05-31 9:00 ` Kevin Wolf
2017-05-30 16:03 ` [Qemu-devel] " Eric Blake
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=20170530153256.GC2665@localhost.localdomain \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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.