diff options
| author | Fernando Luis Vazquez Cao <[email protected]> | 2007-05-09 02:33:28 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2007-05-09 12:30:48 -0700 |
| commit | dd988528f4a7d64908b427c251d727f3c3e88add (patch) | |
| tree | 6a11ed178206e7310be3ddc2524a278db6fec5bb /include/linux/debugobjects.h | |
| parent | a36166c6ef45081fea6eeaf5ca785d7ed786b6e2 (diff) | |
Use the APIC to determine the hardware processor id - x86_64
hard_smp_processor_id used to be just a macro that hard-coded
hard_smp_processor_id to 0 in the non SMP case. When booting non SMP kernels
on hardware where the boot ioapic id is not 0 this turns out to be a problem.
This is happens frequently in the case of kdump and once in a great while in
the case of real hardware.
Use the APIC to determine the hardware processor id in both UP and SMP kernels
to fix this issue.
Notice that hard_smp_processor_id is only used by SMP code or by code that
works with apics so we do not need to handle the case when apics are not
present and hard_smp_processor_id should never be called there.
Signed-off-by: Fernando Luis Vazquez Cao <[email protected]>
Cc: "Luck, Tony" <[email protected]>
Acked-by: Andi Kleen <[email protected]>
Cc: "Eric W. Biederman" <[email protected]>
Cc: Vivek Goyal <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions