qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Benoît Canet" <benoit.canet@gmail.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH V3 0/7] Make QED with live migration safe
Date: Thu, 05 Apr 2012 16:34:54 +0200	[thread overview]
Message-ID: <4F7DAD8E.3030908@redhat.com> (raw)
In-Reply-To: <1332488214-4685-1-git-send-email-benoit.canet@gmail.com>

Am 23.03.2012 08:36, schrieb Benoît Canet:
> This is the third version of a patchset aiming at making the combined
> usage of QED and live migration safe.
> 
> v3:
> 
> -qed: Drop the flags qed structure member and use bs->open_flags to reopen (stefana)
> -qed: When opening honor flags parameter instead of bs->open_flags
> 
> v2:
> 
> -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)
> 
> 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 |   24 +++++++++++++-----------
>  block/qed.h |    2 --
>  blockdev.c  |    4 ++++
>  migration.c |    1 +
>  6 files changed, 30 insertions(+), 13 deletions(-)

Thanks, applied to the block branch.

Kevin

      parent reply	other threads:[~2012-04-05 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  7:36 [Qemu-devel] [PATCH V3 0/7] Make QED with live migration safe Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 1/7] block: Add new BDRV_O_INCOMING flag to notice incoming live migration Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 2/7] block: add a function to clear incoming live migration flags Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 3/7] blockdev: open images with BDRV_O_INCOMING on incoming live migration Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 4/7] qed: add bdrv_invalidate_cache to be called after " Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 5/7] migration: clear BDRV_O_INCOMING flags on end of " Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 6/7] qed: honor BDRV_O_INCOMING for " Benoît Canet
2012-03-23  7:36 ` [Qemu-devel] [PATCH V3 7/7] qed: remove incoming live migration blocker Benoît Canet
2012-03-23 11:24 ` [Qemu-devel] [PATCH V3 0/7] Make QED with live migration safe Stefan Hajnoczi
2012-04-04 16:15   ` Benoît Canet
2012-04-05 14:34 ` Kevin Wolf [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=4F7DAD8E.3030908@redhat.com \
    --to=kwolf@redhat.com \
    --cc=benoit.canet@gmail.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).