[PATCH 1/5] Remove hardcoding of hard_smp_processor_id on UP systems
With the advent of kdump, the assumption that the boot CPU when booting an UP kernel is always the CPU with a hardware ID of 0 (usually referred to as BSP on some architectures) is not valid anymore. Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]> --- diff -urNp linux-2.6.21-rc2/include/linux/smp.h linux-2.6.21-rc2-hwcpuid/include/linux/smp.h --- linux-2.6.21-rc2/include/linux/smp.h2007-02-05 03:44:54.0 +0900 +++ linux-2.6.21-rc2-hwcpuid/include/linux/smp.h2007-03-07 12:02:13.0 +0900 @@ -83,7 +83,6 @@ void smp_prepare_boot_cpu(void); * These macros fold the SMP functionality into a single CPU system */ #define raw_smp_processor_id() 0 -#define hard_smp_processor_id()0 static inline int up_smp_call_function(void) { return 0; - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 1/5] Remove hardcoding of hard_smp_processor_id on UP systems
With the advent of kdump, the assumption that the boot CPU when booting an UP kernel is always the CPU with a hardware ID of 0 (usually referred to as BSP on some architectures) is not valid anymore. Signed-off-by: Fernando Luis Vazquez Cao [EMAIL PROTECTED] --- diff -urNp linux-2.6.21-rc2/include/linux/smp.h linux-2.6.21-rc2-hwcpuid/include/linux/smp.h --- linux-2.6.21-rc2/include/linux/smp.h2007-02-05 03:44:54.0 +0900 +++ linux-2.6.21-rc2-hwcpuid/include/linux/smp.h2007-03-07 12:02:13.0 +0900 @@ -83,7 +83,6 @@ void smp_prepare_boot_cpu(void); * These macros fold the SMP functionality into a single CPU system */ #define raw_smp_processor_id() 0 -#define hard_smp_processor_id()0 static inline int up_smp_call_function(void) { return 0; - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/