[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH V5 0/4] Make OVMF work with Xen



On Fri, Dec 06, 2013 at 10:01:01AM +0100, Fabio Fantoni wrote:
> Il 05/12/2013 18:29, Wei Liu ha scritto:
> >This is version 5 of Xen side patches. Patches that have been applied are not
> >resent.
> >
> >Two patches to build system are added to this series.
> >
> >Still waiting for OVMF side patches to get merged. The main purpose for 
> >sending
> >this series is to let people review the newly added build system patches.
> >
> >Wei.
> >
> >Changes in V5:
> >* add patches for build system
> >
> >Changes in V4:
> >* go back to dedicated OVMF info structure, 64 bit ready
> >
> >Changes in V3:
> >* move seabios_info to common code
> >* e820 entry number is 16 again, one can bump it when necessary
> >* reserve low reset vector in E820 map in OVMF
> >
> >Changes in V2:
> >* ovmf_info is now almost the same as seabios_info
> >* bump e820 entry number to 128
> >* modify build_e820_table to avoid BIOS region reservation if there's none
> >
> >Wei Liu (4):
> >   hvmloader/ovmf: setup ovmf_info
> >   hvmloader/ovmf: setup E820 map
> >   tools: enable OVMF build for Linux by default
> >   tools/ovmf-makefile: only build debug target when specified
> >
> >  tools/configure                 |   24 ++++++++-------
> >  tools/configure.ac              |   17 ++++++++++-
> >  tools/firmware/hvmloader/ovmf.c |   61 
> > +++++++++++++++++++++++++++++++++++++--
> >  tools/firmware/ovmf-makefile    |   19 ++++++++----
> >  4 files changed, 101 insertions(+), 20 deletions(-)
> >
> 
> Is "libxl: bump LIBXL_MAXMEM_CONSTANT to 2048" patch no longer needed?
> 

No, it's not necessary anymore.

Wei.

> Thanks for any reply.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.