Re: [Xen-devel] Xen 4.4 development update: RC0 imminent

[Wei Liu <wei.liu2@xxxxxxxxxx>]

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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel