> We still are stopping all cpus on a panic.
> The difference is that we don't need to move to the boot cpu
> and do this from there, since the new kernel can deal with
> starting from any CPU.
The kernel always supported this - cpu IDs are dynamically assigned on
bootup ... and the boot cpu is always given number 0. There's nothing
magical about the boot CPU, it doesn't really matter which it is. The only
problem we had to fix last night was that the OS believes the BIOS mps
tables as to what the boot CPU is. It now just says ... "oh, I'm the boot
cpu ... because I'm running this code".
This seems infinitely simpler and safer to me than trying to migrate
yourself around (potentially at panic time with a bad kernel). The only
thing that will be different is the *physical* apic id of the CPU, which
nothing uses after we boot anyway.
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:51 EST