qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
	qemu devel <qemu-devel@nongnu.org>,
	Eric Blake <eblake@redhat.com>,
	"eddie . dong" <eddie.dong@intel.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	Bian Naimeng <biannm@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH V6 0/2] Add new qmp commands to suppurt Xen COLO
Date: Mon, 6 Feb 2017 13:13:53 +0000	[thread overview]
Message-ID: <20170206131352.GD2524@work-vm> (raw)
In-Reply-To: <61ae330c-b431-fff3-dd58-ba24b081dc60@redhat.com>

* Jason Wang (jasowang@redhat.com) wrote:
> 
> 
> On 2017年01月26日 11:04, Zhang Chen wrote:
> > Hi~
> > 
> > No news for a week.
> > 
> > We need comments ~~
> > 
> > Ping...
> > 
> 
> Cc David who is one of the maintainer of migration.

My difficulty is I don't know any Xen and I don't understand
the block replication code much either; so I hadn't really looked at it.

Dave

> 
> > 
> > Thanks
> > 
> > Zhang Chen
> > 
> > 
> > On 01/19/2017 05:57 PM, Zhang Chen wrote:
> > > Hi~~
> > > 
> > > Anyone have any comments?
> > > 
> > > Ping....
> > > 
> > > 
> > > Thanks
> > > 
> > > Zhang Chen
> > > 
> > > 
> > > On 01/05/2017 02:08 PM, Zhang Chen wrote:
> > > > Xen COLO depend on qemu COLO replication function.
> > > > So, We need new qmp commands for Xen to use qemu replication.
> > > > 
> > > > Corresponding libxl patches already in xen.git.
> > > > Commit ID:
> > > > 
> > > > ed37ef1f91c20f0ab162ce60f8c38400b917fa64
> > > > COLO: introduce new API to prepare/start/do/get_error/stop replication
> > > > 
> > > > a0ddc0b359375b2418213966dfbdbfab593ecc6f
> > > > tools/libxl: introduction of libxl__qmp_restore to load qemu state
> > > > 
> > > > 
> > > > Zhang Chen (2):
> > > >    Add a new qmp command to start/stop replication
> > > >    Add a new qmp command to do checkpoint, query xen replication status
> > > > 
> > > >   docs/qmp-commands.txt | 42 +++++++++++++++++++++++++++++++
> > > >   migration/colo.c      | 40 +++++++++++++++++++++++++++++
> > > >   qapi-schema.json      | 69
> > > > +++++++++++++++++++++++++++++++++++++++++++++++++++
> > > >   3 files changed, 151 insertions(+)
> > > > 
> > > 
> > 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2017-02-06 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05  6:08 [Qemu-devel] [PATCH V6 0/2] Add new qmp commands to suppurt Xen COLO Zhang Chen
2017-01-05  6:08 ` [Qemu-devel] [PATCH V6 1/2] Add a new qmp command to start/stop replication Zhang Chen
2017-01-05  6:08 ` [Qemu-devel] [PATCH V6 2/2] Add a new qmp command to do checkpoint, query xen replication status Zhang Chen
2017-02-07 15:50   ` Eric Blake
2017-02-08  2:22     ` Zhang Chen
2017-01-19  9:57 ` [Qemu-devel] [PATCH V6 0/2] Add new qmp commands to suppurt Xen COLO Zhang Chen
2017-01-26  3:04   ` Zhang Chen
2017-01-26  3:10     ` Jason Wang
2017-02-06 13:13       ` Dr. David Alan Gilbert [this message]
2017-02-07  2:01         ` Zhang Chen

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=20170206131352.GD2524@work-vm \
    --to=dgilbert@redhat.com \
    --cc=biannm@cn.fujitsu.com \
    --cc=eblake@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --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).