> >> +#ifdef CONFIG_ACPI_PROCESSOR_AGGREGATOR > > > > How does that work when the the driver is booted under baremetal? > > Won't it kick out the native ACPI_PROCESSOR_AGGREGATOR_CLASS > > (acpi_pad.c) ? > > > > What about if the other ACPI_PROCESSOR_AGGREGATOR_CLASS gets called > > first? Won't this fail? > > > > Or is the acpi_bus_register_driver smart enough to process more than > > one ACPI bus device? > > When driver booted under baremetal, xen_acpi_pad.c would be disabled and native acpi_pad.c logic would work. Ah right. It is b/c it uses the pvops indirection mechanism. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
