Re: [PATCH] acpi: try to trust cpu_index from x86_cpu_to_apicid

2014-04-27 Thread Baoquan He
On 04/21/14 at 10:51pm, Rafael J. Wysocki wrote: > On Tuesday, April 15, 2014 07:55:54 AM Baoquan He wrote: > > In smp with multi cpus, when enter into kdump kernel with only 1 cpu, > > a warning message is printed out: > > > > acpi LNXCPU:0a: BIOS reported wrong ACPI id 0 for the processor > > >

Re: [PATCH] acpi: try to trust cpu_index from x86_cpu_to_apicid

2014-04-23 Thread Baoquan He
On 04/21/14 at 10:51pm, Rafael J. Wysocki wrote: > On Tuesday, April 15, 2014 07:55:54 AM Baoquan He wrote: > > In smp with multi cpus, when enter into kdump kernel with only 1 cpu, > > a warning message is printed out: > > > > acpi LNXCPU:0a: BIOS reported wrong ACPI id 0 for the processor > > >

Re: [PATCH] acpi: try to trust cpu_index from x86_cpu_to_apicid

2014-04-21 Thread Rafael J. Wysocki
On Tuesday, April 15, 2014 07:55:54 AM Baoquan He wrote: > In smp with multi cpus, when enter into kdump kernel with only 1 cpu, > a warning message is printed out: > > acpi LNXCPU:0a: BIOS reported wrong ACPI id 0 for the processor > > In this case kdump kernel use the same ACPI tables as 1st ke

[PATCH] acpi: try to trust cpu_index from x86_cpu_to_apicid

2014-04-14 Thread Baoquan He
In smp with multi cpus, when enter into kdump kernel with only 1 cpu, a warning message is printed out: acpi LNXCPU:0a: BIOS reported wrong ACPI id 0 for the processor In this case kdump kernel use the same ACPI tables as 1st kernel, means lapic information is got from MADT. The acpi_id related t