From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Liu <wei.liu2@citrix.com>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Fri, 6 Dec 2013 10:51:44 +0000
Message-ID: <20131206105144.GD32155@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>
	<20131205180357.GC29387@zion.uk.xensource.com>
	<1386322041.20047.145.camel@kazak.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <wei.liu2@citrix.com>) id 1Vot0e-00089m-CC
	for xen-devel@lists.xenproject.org; Fri, 06 Dec 2013 10:51:48 +0000
Content-Disposition: inline
In-Reply-To: <1386322041.20047.145.camel@kazak.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, George Dunlap <george.dunlap@eu.citrix.com>, Vladimir =?utf-8?Q?'=CF=86-coder=2Fphcoder'?= Serbinenko <phcoder@gmail.com>, Fabio Fantoni <fabio.fantoni@heliman.it>, David Vrabel <david.vrabel@citrix.com>, xen-devel <xen-devel@lists.xenproject.org>, Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, Dec 06, 2013 at 09:27:21AM +0000, Ian Campbell wrote:
> On Thu, 2013-12-05 at 18:03 +0000, Wei Liu wrote:
> > 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
> 
> I think that if we are going to commit now without waiting for the OVMF
> side commit first we should omit "enable OVMF build for Linux by
> default".
> 

Yes. We can wait until OVMF side it is upstreamed for this one.

Wei.

> Ian.