From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: Request a freeze exception for COLO in v4.6 Date: Fri, 17 Jul 2015 11:18:21 +0100 Message-ID: <21928.54893.336762.233365@mariner.uk.xensource.com> References: <55A6332D.7070000@cn.fujitsu.com> <20150716150058.GT12455@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150716150058.GT12455@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Ian Campbell , Wen Congyang , Andrew Cooper , Jiang Yunhong , Dong Eddie , "xen-devel@lists.xen.org" , Gui Jianfeng , Yang Hongyang List-Id: xen-devel@lists.xenproject.org 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. 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.