[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [Qemu-devel] [PATCH v5 18/24] hw: i386: Export the MADT build method
On Mon, 5 Nov 2018 02:40:41 +0100 Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> wrote: > It is going to be used by the PC machine type as the MADT table builder > method and thus needs to be exported outside of acpi-build.c > > Also, now that the generic build_madt() API is exported, we have to > rename the ARM static one in order to avoid build time conflicts. > > Reviewed-by: Philippe Mathieu-Daudé <philmd@xxxxxxxxxx> > Tested-by: Philippe Mathieu-Daudé <philmd@xxxxxxxxxx> > Signed-off-by: Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> > --- > include/hw/i386/acpi.h | 28 ++++++++++++++++++++++++++++ > hw/arm/virt-acpi-build.c | 4 ++-- > hw/i386/acpi-build.c | 4 ++-- > 3 files changed, 32 insertions(+), 4 deletions(-) > create mode 100644 include/hw/i386/acpi.h > > diff --git a/include/hw/i386/acpi.h b/include/hw/i386/acpi.h > new file mode 100644 > index 0000000000..b7a887111d > --- /dev/null > +++ b/include/hw/i386/acpi.h [...] > +/* ACPI MADT (Multiple APIC Description Table) build method */ > +void build_madt(GArray *table_data, BIOSLinker *linker, > + MachineState *ms, AcpiConfiguration *conf); > + > +#endif > diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c > index b5e165543a..b0354c5f03 100644 > --- a/hw/arm/virt-acpi-build.c > +++ b/hw/arm/virt-acpi-build.c > @@ -564,7 +564,7 @@ build_gtdt(GArray *table_data, BIOSLinker *linker, > VirtMachineState *vms) > > /* MADT */ > static void > -build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms) > +virt_build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState > *vms) > { You are moving build_madt() into x86 specific header i386/acpi.h so question is why do you touch ARM variant at all? [...] _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |