qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <chen.zhang@intel.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	 "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	qemu-dev <qemu-devel@nongnu.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Paul Durrant <paul.durrant@citrix.com>
Cc: Zhang Chen <zhangckid@gmail.com>
Subject: Re: [Qemu-devel] [PATCH V2 0/5] Add Xen COLO support
Date: Mon, 10 Jun 2019 12:09:04 +0800	[thread overview]
Message-ID: <e02f265c-a0f4-0b34-e3e9-48f0d9eefaf8@redhat.com> (raw)
In-Reply-To: <20190609164433.5866-1-chen.zhang@intel.com>


On 2019/6/10 上午12:44, Zhang Chen wrote:
> From: Zhang Chen <chen.zhang@intel.com>
>
> Xen COLO based on KVM COLO architecture, it shared COLO proxy and block
> replication with KVM COLO. The only differece is Xen COLO have own
> COLO-frame to handle live migration related function, so we need this
> series make Xen COLO frame can communicate with other COLO modules in
> qemu. Xen side related patches have been merged.


Any pointer to this?

Thanks


>
> V2:
>   - Rebase on upstream code.
>   - Optimize code by Zhijian's comments in patch 4/5.
>   - Remove origin 5/6 patch.
>
> V1:
>   - Initial patch.
>
> Zhang Chen (5):
>    COLO-compare: Add new parameter to communicate with remote colo-frame
>    COLO-compare: Add remote notification chardev handler frame
>    COLO-compare: Make the compare_chr_send() can send notification
>      message.
>    COLO-compare: Add colo-compare remote notify support
>    migration/colo.c: Add missed filter notify for Xen COLO.
>
>   migration/colo.c   |   2 +
>   net/colo-compare.c | 155 +++++++++++++++++++++++++++++++++++++++------
>   qemu-options.hx    |  33 +++++++++-
>   3 files changed, 171 insertions(+), 19 deletions(-)
>


  parent reply	other threads:[~2019-06-10  4:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 16:44 [Qemu-devel] [PATCH V2 0/5] Add Xen COLO support Zhang Chen
2019-06-09 16:44 ` [Qemu-devel] [PATCH V2 1/5] COLO-compare: Add new parameter to communicate with remote colo-frame Zhang Chen
2019-06-09 16:44 ` [Qemu-devel] [PATCH V2 2/5] COLO-compare: Add remote notification chardev handler frame Zhang Chen
2019-06-09 16:44 ` [Qemu-devel] [PATCH V2 3/5] COLO-compare: Make the compare_chr_send() can send notification message Zhang Chen
2019-06-09 16:44 ` [Qemu-devel] [PATCH V2 4/5] COLO-compare: Add colo-compare remote notify support Zhang Chen
2019-06-27  1:58   ` Jason Wang
2019-06-27  8:53     ` Zhang, Chen
2019-06-09 16:44 ` [Qemu-devel] [PATCH V2 5/5] migration/colo.c: Add missed filter notify for Xen COLO Zhang Chen
2019-06-10  4:09 ` Jason Wang [this message]
2019-06-10  5:56   ` [Qemu-devel] [PATCH V2 0/5] Add Xen COLO support Zhang, Chen
2019-06-21  6:43     ` Zhang, Chen
2019-06-21  7:25       ` Jason Wang
2019-06-21  7:37         ` Zhang, Chen
2019-07-02  2:00 ` Jason Wang

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=e02f265c-a0f4-0b34-e3e9-48f0d9eefaf8@redhat.com \
    --to=jasowang@redhat.com \
    --cc=chen.zhang@intel.com \
    --cc=dgilbert@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=paul.durrant@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=zhang.zhanghailiang@huawei.com \
    --cc=zhangckid@gmail.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).