From: "Benoît Canet" <benoit.canet@gmail.com>
To: kwolf@redhat.com
Cc: stefanha@gmail.com, qemu-devel@nongnu.org,
stefanha@linux.vnet.ibm.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3 0/7] Make QED with live migration safe
Date: Wed, 4 Apr 2012 18:15:28 +0200 [thread overview]
Message-ID: <CAOh3yayrik0VDx+JTz3tPEtLG-UUdBypF0+A6UYqhoCkR3b92A@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QXvttmtY9r0unGe1J6yCuQ8fAsHsEZyciFUt30oHRzbxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 248 bytes --]
>
>
>
> I tested qed live migration as well as confirming that bs->open_flags
> BDRV_O_INCOMING works correctly in gdb.
>
> Reviewed-by: Stefan Hajnoczi <stefanha@gmail.com>
>
ping.
Kevin Wolf: will it be merged in your next for-anthony branch ?
[-- Attachment #2: Type: text/html, Size: 872 bytes --]
next prev parent reply other threads:[~2012-04-04 16:15 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 [this message]
2012-04-05 14:34 ` Kevin Wolf
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=CAOh3yayrik0VDx+JTz3tPEtLG-UUdBypF0+A6UYqhoCkR3b92A@mail.gmail.com \
--to=benoit.canet@gmail.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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 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.