From: Amit Shah <amit.shah@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, dgilbert@redhat.com,
peter.huangpeng@huawei.com, eddie.dong@intel.com,
wency@cn.fujitsu.com, lizhijian@cn.fujitsu.com,
zhangchen.fnst@cn.fujitsu.com, xiecl.fnst@cn.fujitsu.com,
Gonglei <arei.gonglei@huawei.com>
Subject: Re: [Qemu-devel] [PATCH COLO-Frame v18 01/34] configure: Add parameter for configure to enable/disable COLO support
Date: Fri, 26 Aug 2016 03:15:48 +0530 [thread overview]
Message-ID: <20160825214548.GA13560@localhost.localdomain> (raw)
In-Reply-To: <1470227172-13704-2-git-send-email-zhang.zhanghailiang@huawei.com>
On (Wed) 03 Aug 2016 [20:25:39], zhanghailiang wrote:
> configure --enable-colo/--disable-colo to switch COLO
> support on/off.
> COLO support is On by default.
Can you please make this the last patch in the series - so we get the
code in before we add in the config option? Better for bisection, but
also for a logical flow.
Thanks,
Amit
next prev parent reply other threads:[~2016-08-25 21:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 12:25 [Qemu-devel] [PATCH COLO-Frame v18 00/34] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 01/34] configure: Add parameter for configure to enable/disable COLO support zhanghailiang
2016-08-25 21:45 ` Amit Shah [this message]
2016-09-01 3:26 ` Hailiang Zhang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 02/34] migration: Introduce capability 'x-colo' to migration zhanghailiang
2016-08-25 21:47 ` Amit Shah
2016-09-01 3:27 ` Hailiang Zhang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 03/34] COLO: migrate colo related info to secondary node zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 04/34] migration: Integrate COLO checkpoint process into migration zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 05/34] migration: Integrate COLO checkpoint process into loadvm zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 06/34] COLO/migration: Create a new communication path from destination to source zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 07/34] COLO: Implement COLO checkpoint protocol zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 08/34] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 09/34] COLO: Save PVM state to secondary side when do checkpoint zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 10/34] COLO: Load PVM's dirty pages into SVM's RAM cache temporarily zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 11/34] ram/COLO: Record the dirty pages that SVM received zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 12/34] COLO: Load VMState into buffer before restore it zhanghailiang
2016-08-05 17:53 ` Dr. David Alan Gilbert
2016-08-08 8:52 ` Daniel P. Berrange
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 13/34] COLO: Flush PVM's cached RAM into SVM's memory zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 14/34] COLO: Add checkpoint-delay parameter for migrate-set-parameters zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 15/34] COLO: Synchronize PVM's state to SVM periodically zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 16/34] COLO failover: Introduce a new command to trigger a failover zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 17/34] COLO failover: Introduce state to record failover process zhanghailiang
2016-08-09 9:17 ` Dr. David Alan Gilbert
2016-08-10 4:07 ` Hailiang Zhang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 18/34] COLO: Implement failover work for Primary VM zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 19/34] COLO: Implement failover work for Secondary VM zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 20/34] qmp event: Add COLO_EXIT event to notify users while exited from COLO zhanghailiang
2016-08-03 12:25 ` [Qemu-devel] [PATCH COLO-Frame v18 21/34] COLO failover: Shutdown related socket fd when do failover zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 22/34] COLO failover: Don't do failover during loading VM's state zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 23/34] COLO: Process shutdown command for VM in COLO state zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 24/34] COLO: Update the global runstate after going into colo state zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 25/34] savevm: Introduce two helper functions for save/find loadvm_handlers entry zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 26/34] migration/savevm: Add new helpers to process the different stages of loadvm zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 27/34] migration/savevm: Export two helper functions for savevm process zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 28/34] COLO: Separate the process of saving/loading ram and device state zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 29/34] COLO: Split qemu_savevm_state_begin out of checkpoint process zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 30/34] filter-buffer: Accept zero interval zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 31/34] net: Add notifier/callback for netdev init zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 32/34] COLO/filter: Add each netdev a buffer filter zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 33/34] COLO: Control the status of buffer filters for PVM zhanghailiang
2016-08-03 12:26 ` [Qemu-devel] [PATCH COLO-Frame v18 34/34] COLO: Add block replication into colo process zhanghailiang
2016-08-16 0:00 ` [Qemu-devel] [PATCH COLO-Frame v18 00/34] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) Changlong Xie
2016-08-16 10:51 ` Hailiang Zhang
[not found] ` <CAEH94Lju9VSjxo_32yX2iTJngapfDiKQrSXVHa6G6S05yCFWeg@mail.gmail.com>
2016-08-17 5:46 ` Changlong Xie
2016-08-25 21:52 ` Amit Shah
2016-09-01 8:03 ` Hailiang Zhang
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=20160825214548.GA13560@localhost.localdomain \
--to=amit.shah@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.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=zhang.zhanghailiang@huawei.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 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).