From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: Xen 4.4 development update: RC0 imminent Date: Thu, 5 Dec 2013 18:03:57 +0000 Message-ID: <20131205180357.GC29387@zion.uk.xensource.com> References: <20131205163425.GA27631@zion.uk.xensource.com> <52A0AC3F.2010605@eu.citrix.com> <20131205164841.GB27631@zion.uk.xensource.com> <1386262760.20047.130.camel@kazak.uk.xensource.com> <20131205170652.GA29387@zion.uk.xensource.com> <1386263815.20047.137.camel@kazak.uk.xensource.com> <20131205173425.GB29387@zion.uk.xensource.com> <52A0BD91.9060704@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 1VodHO-0004gK-Gg for xen-devel@lists.xenproject.org; Thu, 05 Dec 2013 18:04:02 +0000 Content-Disposition: inline In-Reply-To: <52A0BD91.9060704@eu.citrix.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: George Dunlap Cc: Wei Liu , Ian Campbell , Vladimir =?utf-8?Q?'=CF=86-coder=2Fphcoder'?= Serbinenko , Fabio Fantoni , David Vrabel , xen-devel , Roger Pau =?iso-8859-1?Q?Monn=E9?= List-Id: xen-devel@lists.xenproject.org On Thu, Dec 05, 2013 at 05:53:21PM +0000, George Dunlap wrote: [...] > >>OK, so I'm clearly in two minds about this ;-) > >> > >>George -- what do you think? > >> > >My two cents would be let's see if we can upstream OVMF side patches in > >time (it looks quite close now but I cannot say for sure, it's not > >controlled by us ;-)), then release it in 4.4 and mark this feature as > >experimental. Otherwise there's no need to merge Xen side patches. > > In time for what? > I mean to have those OVMF side patches applied to upstream tree within certain time frame then we can push those changes to our tree and publish a hash in Config.mk in time for 4.4. > Like I said, I think downloading a repo / tarball and building it is > much lower than applying patches and then building. And changing > editing the one file in the Xen tree that has the commit hash is > easier yet. So I think there's an advantage to checking them in > even if OVMF isn't upstream by the time we release. > I guess this would work as well. > And since OVMF is broken now anyway, we can't really break it; so > there's little risk. :-) > Right. I certainly cannot make it more broken than what we had in 4.3. :-P Wei. > -George