From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: zhang.zhanghailiang@huawei.com, zhangchen.fnst@cn.fujitsu.com,
lizhijian@cn.fujitsu.com, xiecl.fnst@cn.fujitsu.com,
wency@cn.fujitsu.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] COLO hybrid mode and other changes
Date: Thu, 21 Jan 2016 19:08:44 +0000 [thread overview]
Message-ID: <20160121190843.GH2446@work-vm> (raw)
Hi,
I've got a world with a few COLO changes in that you might
like to look at; they're all experimental, but it seems
to be working for me.
The world is at:
https://github.com/orbitfp7/qemu/commits/orbit-wp4-colo-jan16
It's based off:
The December/2.4 colo framework world with periodic checkpoints
+ The december user space colo-proxy
+ The integration code that was in the colo-proxy git repo
(those needed some updates to go into the 2.4-periodic world)
And then I've added:
- An updated version of my hybrid mode code that switches between
COLO and periodic checkpoints depending on the frequency of
miscompares
- A minimum checkpoint time, so that on fast miscompares
we do get some runtime (as in the earlier colo series)
- I'm using a condition-variable to flag the miscompares from
the colo-proxy to the colo thread; this seems cleaner and it
avoids having to do short waits; it might be a bit tricky
to make portable.
- Add back some statistcs in 'info migrate'
- An HMP command equivalent to x-blockdev-change.
- RDMA transport for COLO
I don't intend to post any of these changes in full to the list
until your main COLO code is in; although if any of my changes
are useful to you, then feel free to include them in sets you post.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2016-01-21 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 19:08 Dr. David Alan Gilbert [this message]
2016-01-22 3:04 ` [Qemu-devel] COLO hybrid mode and other changes 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=20160121190843.GH2446@work-vm \
--to=dgilbert@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--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 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.