Re: [Xen-devel] [PATCH] Config.mk: update OVMF changeset

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2013-12-09 at 11:17 +0000, George Dunlap wrote:
> On 12/09/2013 11:10 AM, Wei Liu wrote:
> > On Mon, Dec 09, 2013 at 11:04:23AM +0000, George Dunlap wrote:
> >> On 12/08/2013 08:50 PM, Wei Liu wrote:
> >>> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
> >>> Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
> >>> Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> >>> Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
> >> This lacks a description of what the effect will be of updating to
> >> this changeset.  I'm guessing that the OVMF side of your recent
> >> fixes have gotten checked in?
> >>
> > Yes, necessary patches to integrate OVMF with Xen is upstreamed now.
> >
> > The original changeset in Config.mk:
> > 1. doesn't work with guest > 4G ram
> > 2. messes up PCI resource mapping
> >
> > The version of OVMF fixes those bugs and works well for me.
> 
> re the interface, we generally plan on building OVMF ourselves, right?  
> I don't think the interface between Xen and OVMF necessarily needs to be 
> stable at this point.

It is an ABI between Xen and an external 3rd party codebase. Although we
might build it ourselves by default we cannot enforce this, and our
users might use e.g. their distro binary. This is similar to the
situation with upstream qemu.

This ABI absolutely has to be stable from now on (or make use of the
inbuilt capability to extend itself).

I don't think there is going to be any reason for this interface to
change so this is fine.

> In any case, the interface changes are already in Xen; this doesn't make 
> the interface available, it just makes it easier for people to build OVMF.
> 
> Release-acked-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>



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