diff options
author | Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp> | 2007-05-09 02:33:27 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-05-09 12:30:48 -0700 |
commit | a36166c6ef45081fea6eeaf5ca785d7ed786b6e2 (patch) | |
tree | bdb5a99e3c80883cbb84d6e190b4dabefec79032 /include/asm-x86_64 | |
parent | 2f4dfe206a2fc07099dfad77a8ea2f4b4ae2140f (diff) | |
download | kernel_samsung_aries-a36166c6ef45081fea6eeaf5ca785d7ed786b6e2.zip kernel_samsung_aries-a36166c6ef45081fea6eeaf5ca785d7ed786b6e2.tar.gz kernel_samsung_aries-a36166c6ef45081fea6eeaf5ca785d7ed786b6e2.tar.bz2 |
Use the APIC to determine the hardware processor id - i386
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 <fernando@oss.ntt.co.jp>
Cc: "Luck, Tony" <tony.luck@intel.com>
Acked-by: Andi Kleen <ak@suse.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/asm-x86_64')
0 files changed, 0 insertions, 0 deletions