From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
quintela@redhat.com, dgilbert@redhat.com, wency@cn.fujitsu.com,
lizhijian@cn.fujitsu.com, zhangchen.fnst@cn.fujitsu.com,
xiecl.fnst@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH COLO-Frame v19 00/22] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT)
Date: Tue, 13 Sep 2016 09:04:23 +0800 [thread overview]
Message-ID: <57D75097.1000306@huawei.com> (raw)
In-Reply-To: <20160910082119.GB3822@amit-lp.rh>
On 2016/9/10 16:21, Amit Shah wrote:
> Hi,
>
> On (Fri) 09 Sep 2016 [14:45:36], Hailiang Zhang wrote:
>> ping ?
>
> Juan will start reviewing and picking patches soon.
>
Great, and the pull request of block replication series has
been sent by Stefan, so there is no obstacle to impede this
series to be merged into upstream. Thanks very much ;)
>
> .
>
prev parent reply other threads:[~2016-09-13 1:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 3:24 [Qemu-devel] [PATCH COLO-Frame v19 00/22] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 01/22] migration: Introduce capability 'x-colo' to migration zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 02/22] COLO: migrate COLO related info to secondary node zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 03/22] migration: Enter into COLO mode after migration if COLO is enabled zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 04/22] migration: Switch to COLO process after finishing loadvm zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 05/22] COLO: Establish a new communicating path for COLO zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 06/22] COLO: Introduce checkpointing protocol zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 07/22] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 08/22] COLO: Send PVM state to secondary side when do checkpoint zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 09/22] COLO: Load VMState into QIOChannelBuffer before restore it zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 10/22] COLO: Add checkpoint-delay parameter for migrate-set-parameters zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 11/22] COLO: Synchronize PVM's state to SVM periodically zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 12/22] COLO: Add 'x-colo-lost-heartbeat' command to trigger failover zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 13/22] COLO: Introduce state to record failover process zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 14/22] COLO: Implement the process of failover for primary VM zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 15/22] COLO: Implement failover work for secondary VM zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 16/22] COLO: Shutdown related socket fd while do failover zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 17/22] COLO: Don't do failover while loading VM's state zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 18/22] COLO: Handle shutdown command for VM in COLO state zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 19/22] COLO: Update the global runstate after going into colo state zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 20/22] COLO: Add block replication into colo process zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 21/22] docs: Add documentation for COLO feature zhanghailiang
2016-09-01 3:24 ` [Qemu-devel] [PATCH COLO-Frame v19 22/22] configure: Support enable/disable " zhanghailiang
2016-09-01 3:57 ` [Qemu-devel] [PATCH COLO-Frame v19 00/22] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) no-reply
2016-09-09 6:45 ` Hailiang Zhang
2016-09-10 8:21 ` Amit Shah
2016-09-13 1:04 ` Hailiang Zhang [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=57D75097.1000306@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wency@cn.fujitsu.com \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=zhangchen.fnst@cn.fujitsu.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.