qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Benoît Canet" <benoit.canet@gmail.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, wolf@redhat.com,
	stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH 02/10] block: add a function to set incoming live migration
Date: Tue, 20 Mar 2012 15:57:35 +0000	[thread overview]
Message-ID: <20120320155735.GC896@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1331055149-10982-3-git-send-email-benoit.canet@gmail.com>

On Tue, Mar 06, 2012 at 06:32:21PM +0100, Benoît Canet wrote:
> This function will help to inform the block layer that an incoming
> live migration is coming in order to make proper usage of the
> BDRV_O_INCOMING flag.
> 
> Signed-off-by: Benoit Canet <benoit.canet@gmail.com>
> ---
>  block.c |    8 ++++++++
>  block.h |    2 ++
>  2 files changed, 10 insertions(+), 0 deletions(-)

The block layer doesn't need to keep track of incoming migrations:

blockdev.c:drive_init() or vl.c:drive_init_func() could use
runstate_check(RUN_STATE_INMIGRATE) to check whether incoming migration
is in progress.  If so, they would pass in BDRV_O_INCOMING during image
creation.  As a result we don't need to introduce this global variable
or functions to manipulate it in the block layer.

The block layer post migration function will still need to clear
BDRV_O_INCOMING from open_flags.

Stefan

  reply	other threads:[~2012-03-20 15:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 17:32 [Qemu-devel] [RFC PATCH 00/10] make qed and live migration usage safe Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 01/10] block: Add new BDRV_O_INCOMING flag to notice incoming live migration Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 02/10] block: add a function to set " Benoît Canet
2012-03-20 15:57   ` Stefan Hajnoczi [this message]
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 03/10] block: add a function to clear " Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 04/10] block: rename *_invalidate_cache_* to *_post_incoming_migration_* Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 05/10] migration: inform the block layer of incoming live status Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 06/10] block: open images with BDRV_O_INCOMING on incoming live migration Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 07/10] qed: extract image checking into check_image_if_needed Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 08/10] qed: add bdrv_post_incoming_migration operation checking the image Benoît Canet
2012-03-20 15:42   ` Stefan Hajnoczi
2012-03-20 15:52     ` Benoît Canet
2012-03-20 16:05       ` Stefan Hajnoczi
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 09/10] qed: honor BDRV_O_INCOMING for incoming live migration Benoît Canet
2012-03-06 17:32 ` [Qemu-devel] [RFC PATCH 10/10] qed: remove incoming live migration blocker Benoît Canet
2012-03-06 20:10 ` [Qemu-devel] [RFC PATCH 00/10] make qed and live migration usage safe Benoît Canet
2012-03-16 12:40 ` Benoît Canet
2012-03-20 15:47 ` Stefan Hajnoczi

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=20120320155735.GC896@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=benoit.canet@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=wolf@redhat.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).