On Fri, Mar 04, 2016 at 10:57:59AM +, Andrew Cooper wrote:
> On 03/03/16 18:03, Anthony PERARD wrote:
> > In this series, there are plenty of places where one blob loaded by libxl
> > to be consume by hvmloader is called acpi_module or acpi_table... where in
> > fact it is only the DSDT table.
On 03/03/16 18:03, Anthony PERARD wrote:
> In this series, there are plenty of places where one blob loaded by libxl
> to be consume by hvmloader is called acpi_module or acpi_table... where in
> fact it is only the DSDT table. I think I'm going to do some renaming to
> include "dsdt" into those
In this series, there are plenty of places where one blob loaded by libxl
to be consume by hvmloader is called acpi_module or acpi_table... where in
fact it is only the DSDT table. I think I'm going to do some renaming to
include "dsdt" into those names.
--
Anthony PERARD
On Thu, Feb 25, 2016 at 11:16:18AM -0500, Boris Ostrovsky wrote:
> On 02/25/2016 09:55 AM, Anthony PERARD wrote:
> >Hi all,
> >
> >Many changes in V3:
> > no more cmdline, but use each modules' cmdline to provide a name for it.
> > in libxc:
> > - use xc_dom_alloc_segment() to load
On 02/25/2016 09:55 AM, Anthony PERARD wrote:
Hi all,
Many changes in V3:
no more cmdline, but use each modules' cmdline to provide a name for it.
in libxc:
- use xc_dom_alloc_segment() to load modules. see patch #1.
- avoid duplication of code between PVHv2 and hvmloader for
Hi all,
Many changes in V3:
no more cmdline, but use each modules' cmdline to provide a name for it.
in libxc:
- use xc_dom_alloc_segment() to load modules. see patch #1.
- avoid duplication of code between PVHv2 and hvmloader for the
initialisation of hvm_start_info.
in
