[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 02/19] acpi/hvmloader: Collect processor and NUMA info in hvmloader
>>> On 07.09.16 at 20:59, <boris.ostrovsky@xxxxxxxxxx> wrote: > Changes in v3: > * Constified acpi_numa's pointers > * Constified acpi_config call parameter where possible Thanks, but how about ... > --- a/tools/firmware/hvmloader/acpi/build.c > +++ b/tools/firmware/hvmloader/acpi/build.c > @@ -70,18 +70,20 @@ static void set_checksum( > p[checksum_offset] = -sum; > } > > -static struct acpi_20_madt *construct_madt(struct acpi_info *info) > +static struct acpi_20_madt *construct_madt(const struct acpi_config *config, > + struct acpi_info *info) > { > struct acpi_20_madt *madt; > struct acpi_20_madt_intsrcovr *intsrcovr; > struct acpi_20_madt_ioapic *io_apic; > struct acpi_20_madt_lapic *lapic; > + struct hvm_info_table *hvminfo = config->hvminfo; ... this? > --- a/tools/firmware/hvmloader/acpi/libacpi.h > +++ b/tools/firmware/hvmloader/acpi/libacpi.h > @@ -20,6 +20,8 @@ > #ifndef __LIBACPI_H__ > #define __LIBACPI_H__ > > +#include <xen/memory.h> Why? struct xen_vmemrange doesn't get instantiated anywhere in this header. > @@ -49,6 +59,9 @@ struct acpi_config { > uint32_t length; > } pt; > > + struct acpi_numa numa; > + struct hvm_info_table *hvminfo; And this cannot be const? Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |