Messages in this thread | | | Date | Sat, 26 Oct 2002 08:03:45 -0700 | From | "Martin J. Bligh" <> | Subject | Re: [PATCH] Double x86 initialise fix. |
| |
>>> Isn't this always the case on x86 ? >>> /me waits to hear gory details of some IBM monster. >> >> It isnt. The boot CPU may be any number. In addition you can strap dual >> pentium boxes to arbitrate for who is boot cpu (this is used for fault >> tolerance). > > Eh? I don't understand this, and I think Dave is right for all the > IBM monsters I know of ;-) The *apicid* may not be 0 but the CPU > numbers are dynamically assigned as we boot, so the boot CPU will > always get 0, surely?
Indeed cscope indicates these are acutally hardcoded into the calls:
1 smpboot.c smp_callin 418 smp_store_cpu_info(cpuid); 2 smpboot.c smp_boot_cpus 989 smp_store_cpu_info(0);
The only thing that does smp_callin is a secondary ... so the boot CPU has this hardcoded to 0 ... I think Dave's fine.
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/
| |