From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: qemu devel <qemu-devel@nongnu.org>, Jason Wang <jasowang@redhat.com>
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
"eddie . dong" <eddie.dong@intel.com>,
bian naimeng <biannm@cn.fujitsu.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: [Qemu-devel] [PATCH 0/3] COLO-compare: Make COLO-compare support Xen
Date: Tue, 28 Feb 2017 18:48:19 +0800 [thread overview]
Message-ID: <1488278902-11223-1-git-send-email-zhangchen.fnst@cn.fujitsu.com> (raw)
This series focus on COLO Xen support.
We add a new chardev socket in colo-compare as the way
of communicate with Xen COLO-frame.
Xen part:
https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg02067.html
This series is a frame, have some TODO job depend on this patch:
https://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg05055.html
Zhang Chen (3):
COLO-compare: Add new parameter for communicate with Xen colo-frame
COLO-compare: Add Xen notify chardev socket handler frame
COLO-compare: Add colo-compare Xen notify
net/colo-compare.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
qemu-options.hx | 38 ++++++++++++++++++++++++---
2 files changed, 111 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-28 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 10:48 Zhang Chen [this message]
2017-02-28 10:48 ` [Qemu-devel] [PATCH 1/3] COLO-compare: Add new parameter for communicate with Xen colo-frame Zhang Chen
2017-02-28 10:48 ` [Qemu-devel] [PATCH 2/3] COLO-compare: Add Xen notify chardev socket handler frame Zhang Chen
2017-02-28 10:48 ` [Qemu-devel] [PATCH 3/3] COLO-compare: Add colo-compare Xen notify Zhang Chen
2017-03-13 6:18 ` [Qemu-devel] [PATCH 0/3] COLO-compare: Make COLO-compare support Xen Zhang Chen
2017-03-13 6:28 ` Jason Wang
2017-03-13 7:10 ` Zhang Chen
2017-03-13 7:21 ` Zhang Chen
2017-03-14 7:37 ` Jason Wang
2017-03-14 8:18 ` 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=1488278902-11223-1-git-send-email-zhangchen.fnst@cn.fujitsu.com \
--to=zhangchen.fnst@cn.fujitsu.com \
--cc=biannm@cn.fujitsu.com \
--cc=eddie.dong@intel.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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).