![]() | ||||||||||
Messages in this thread |
Vivek Goyal <vgoyal@in.ibm.com> writes: > You are right. hard_smp_processor_id() is hard-coded to zero in case of a > non SMP kernel (include/linux/smp.h) and that's why the problem is happening. > I am booting a non-SMP capture kernel. In case of kexec on panic, we can very > well boot on a cpu whose id is not zero. > > I have attached a patch with the mail which is now using > boot_cpu_physical_apicid to hard set presence of boot cpu instead of > hard_smp_processor_id(). But the interesting questoin remains why BIOS is > not reporting the boot cpu. Ok this looks good. But it raises a couple of followup questions. - Are there other places that use hard_smp_processor_id in in a uniprocessor kernel? - Does x86_64 have this same problem? Anyway it looks like we have this working which is a big step forward in having a reliable kdump mechanism. Eric - 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/ | |||||||||
| Last update: 2005-10-24 15:40 [from the cache] ©2003-2008 | ||||||||||