Re: [PATCH] x86/acpi: keep x86_cpu_to_acpiid mapping valid on cpu hotplug

2017-02-07 Thread Vitaly Kuznetsov
"Rafael J. Wysocki" writes: > On Mon, Feb 6, 2017 at 6:01 PM, Vitaly Kuznetsov wrote: >> We may or may not have all possible CPUs in MADT on boot but in any case >> we're overwriting x86_cpu_to_acpiid mapping with U32_MAX when >> acpi_register_lapic() is called again on the CPU hotplug path: >>

Re: [PATCH] x86/acpi: keep x86_cpu_to_acpiid mapping valid on cpu hotplug

2017-02-06 Thread Rafael J. Wysocki
On Mon, Feb 6, 2017 at 6:01 PM, Vitaly Kuznetsov wrote: > We may or may not have all possible CPUs in MADT on boot but in any case > we're overwriting x86_cpu_to_acpiid mapping with U32_MAX when > acpi_register_lapic() is called again on the CPU hotplug path: > acpi_processor_hotadd_init() -> acpi

[PATCH] x86/acpi: keep x86_cpu_to_acpiid mapping valid on cpu hotplug

2017-02-06 Thread Vitaly Kuznetsov
We may or may not have all possible CPUs in MADT on boot but in any case we're overwriting x86_cpu_to_acpiid mapping with U32_MAX when acpi_register_lapic() is called again on the CPU hotplug path: acpi_processor_hotadd_init() -> acpi_map_cpu() -> acpi_register_lapic(). As we have the required acp