From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Wen Congyang <wency@cn.fujitsu.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Subject: Re: Request a freeze exception for COLO in v4.6
Date: Mon, 20 Jul 2015 15:27:18 +0800 [thread overview]
Message-ID: <55ACA2D6.5020403@cn.fujitsu.com> (raw)
In-Reply-To: <21928.54893.336762.233365@mariner.uk.xensource.com>
On 07/17/2015 06:18 PM, Ian Jackson wrote:
> Wei Liu writes ("Re: [Xen-devel] Request a freeze exception for COLO in v4.6"):
>> Ian and Ian, anything to add? What are your opinions?
>
> I think COLO is an exciting and important feature.
>
> Unfortunately I agree with Wei that at this stage taking both series
> as they currently stand into 4.6 is not tenable. (Perhaps if I had
> been able to help earlier in the release cycle this would have been
> different; so for that I'm sorry.)
>
>
> I would like to see at least the early parts of `COLOPre' in staging
> as soon as possible. There is much preparatory work there which would
> be annoying to rebase around, and which has collateral benefits.
Thanks, if you are going to merge some of the patches, there is the
latest version of `COLOPre' patchset:
https://github.com/macrosheep/xen/tree/colo-v9
The latest 26 commits.
I think all patches are ready to be merged except:
7 libxl/remus: init checkpoint_callback in Remus checkpoint callback
11 tools/libxc: support to resume uncooperative HVM guests
20 tools/libx{l,c}: add back channel to libxc
>
> If I can take one example, 11/25 "tools/libxc: support to resume
> uncooperative HVM guests". Based on my current understanding this is
> even a bugfix. Sadly it is not quite ready (or at least, wasn't last
> night). But with a few more days we can probably get much of this
> cleanup and preparatory work in.
>
>
> Assuming nothing goes horribly wrong, I am very optimistic about COLO
> making it upstream soon, just not in 4.6.
>
> Thanks,
> Ian.
> .
>
--
Thanks,
Yang.
next prev parent reply other threads:[~2015-07-20 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 10:17 Request a freeze exception for COLO in v4.6 Yang Hongyang
2015-07-16 15:00 ` Wei Liu
2015-07-17 0:15 ` Dong, Eddie
2015-07-17 10:18 ` Ian Jackson
2015-07-17 10:52 ` Wei Liu
2015-07-20 7:27 ` Yang Hongyang [this message]
2015-07-21 13:42 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2015-07-17 16:04 Eddie Dong
2015-07-20 14:02 ` Lars Kurth
2015-07-20 15:55 ` Lars Kurth
2015-07-17 16:29 Eddie Dong
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=55ACA2D6.5020403@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=wei.liu2@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=yunhong.jiang@intel.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.