From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.4 development update: Is PVH a blocker? Date: Tue, 17 Dec 2013 14:13:30 +0000 Message-ID: <52B05C0A.4040404@eu.citrix.com> References: <52AECC1B020000780010D80B@nat28.tlf.novell.com> <20131217115805.GD32721@deinos.phlegethon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsvOy-0000lB-AR for xen-devel@lists.xenproject.org; Tue, 17 Dec 2013 14:13:36 +0000 In-Reply-To: <20131217115805.GD32721@deinos.phlegethon.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tim Deegan , Jan Beulich Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 12/17/2013 11:58 AM, Tim Deegan wrote: > At 08:47 +0000 on 16 Dec (1387180027), Jan Beulich wrote: >>>>> On 13.12.13 at 20:21, George Dunlap wrote: >>> This information will be mirrored on the Xen 4.4 Roadmap wiki page: >>> http://wiki.xen.org/wiki/Xen_Roadmap/4.4 >>> >>> Our timeline had us start the code freeze last Friday. However, we >>> have not released an RC0 because we have been waiting for PVH dom0 >>> support. Adding bug fixes during RCs makes sense, but RC0 should >>> contain all of the functionality we expect to be in the final release. >>> >>> PVH dom0 support is making progress, however it's not that clear when >>> it will actually be ready to be checked in. The current discussion is >>> about refcounting the new p2m type, which is a tricky and delicate >>> operation (though luckily one which should be limited to domains which >>> use that type -- at the moment, exclusively PVH dom0s). >>> >>> If we continue to wait, it is likely that the release will slip. The >>> question >>> then is, how long should we continue to wait before we cut our losses and >>> say we'll wait for PVH dom0 until 4.5? >> >> Even if likely unpopular, given the condition the one critical patch >> is in I'd favor not waiting any longer at all, deferring the feature >> to 4.5 and cutting RC1 e.g. based on what got pushed over the >> weekend. > > +1. The remeining changes that I'm aware of touch non-pvh code and > refcounting code, neither of which seems like a good idea at this > point, even if they were complete. Right -- I think we're going to have to go ahead without it then. FWIW I was always expecting dom0 PVH not to make it; it was Jan who first suggested making it a blocker. But I think that was before we realized how tricky the p2m stuff was going to be. I haven't taken a close look at the patches, but browsing the conversation, it seems like waiting is the best option. For refcounting in particular, we don't want to rush things. Bugs are subtle and may not manifest for quite a while. It would be better to check this in at the beginning of a release cycle and we had the full time to shake things out. -George