From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: jasowang@redhat.com, zhangchen.fnst@cn.fujitsu.com,
lizhijian@cn.fujitsu.com
Cc: qemu-devel@nongnu.org, xuquan8@huawei.com,
pss.wulizhen@huawei.com,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: [Qemu-devel] [PATCH v2 0/4] colo-compare: fix some bugs
Date: Thu, 16 Feb 2017 14:00:17 +0800 [thread overview]
Message-ID: <1487224821-120916-1-git-send-email-zhang.zhanghailiang@huawei.com> (raw)
This series includes two parts: codes optimization and bug fix.
patch 1 tries to move timer process into colo compare thread as
a new coroutine.
patch 2 ~ 4 fixe some bugs of colo compare.
v2:
- Squash patch 3 of last version into patch 2. (ZhangChen's suggestion)
zhanghailiang (4):
colo-compare: use g_timeout_source_new() to process the stale packets
colo-compare: kick compare thread to exit after some cleanup in
finalization
char: remove the right fd been watched in qemu_chr_fe_set_handlers()
colo-compare: Fix removing fds been watched incorrectly in
finalization
chardev/char-io.c | 13 ++++--
chardev/char-io.h | 2 +
chardev/char.c | 2 +-
net/colo-compare.c | 115 +++++++++++++++++++++++++++--------------------------
4 files changed, 71 insertions(+), 61 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-02-16 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 6:00 zhanghailiang [this message]
2017-02-16 6:00 ` [Qemu-devel] [PATCH v2 1/4] colo-compare: use g_timeout_source_new() to process the stale packets zhanghailiang
2017-02-16 6:00 ` [Qemu-devel] [PATCH v2 2/4] colo-compare: kick compare thread to exit after some cleanup in finalization zhanghailiang
2017-02-16 6:00 ` [Qemu-devel] [PATCH v2 3/4] char: remove the right fd been watched in qemu_chr_fe_set_handlers() zhanghailiang
2017-02-16 10:40 ` Marc-André Lureau
2017-02-16 12:49 ` Hailiang Zhang
2017-02-16 13:04 ` Marc-André Lureau
2017-02-16 13:09 ` Hailiang Zhang
2017-02-16 6:00 ` [Qemu-devel] [PATCH v2 4/4] colo-compare: Fix removing fds been watched incorrectly in finalization zhanghailiang
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=1487224821-120916-1-git-send-email-zhang.zhanghailiang@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pss.wulizhen@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=xuquan8@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 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.