On Mon, Sep 02, 2013 at 11:32:59AM +0900, HATAYAMA Daisuke wrote: > As you suggest, boot_cpu seems more understandable also to me. BTW, > please notice that it doesn't denote that the CPU we're booting on > currently, but that the CPU with BSP flag set. Hmm, by "BSP flag set" you mean it is the first LAPIC entry in the MADT, correct? At least this is the case when you set isbsp to true. Because, there's also the BSC flag in APIC_BAR (MSR 0x1b) which denotes the bootstrapping core on node 0. > In general, current code uses many terms to denote the cpu that is run > at kernel boot-up processing such as boot cpu, bsp, cpu0 and possibly > others since in usual situation, boot cpu is always BSP and assigned > to cpu0. But it is not the case in case of kexec. I'm using the word > bsp purposely in the isbsp to mean the CPU with BSP flag set. > > So I think it's better to use bsp_cpu here to denote the CPU with BSP > flag set. Right. > For the comment, how about the following one? > > /* > * In this case, boot cpu is AP. This can happen on > * kexec/kdump. Consider the case that crash happens on some > * AP and enters kdump 2nd kernel with the AP. > * > * Then, there's issue that if we send INIT to BSP, due to x86 > * hardware specification, it is forced to jump at BIOS init > * code and system hangs or resets immediately. > * > * To avoid the issue, we disable BSP. Then, there's no longer > * possbility to send INIT to BSP. > */ Yes, much better. Especially when looking down the road and people have forgotten what the whole fuss was about, a nice detailed comment is priceless. Thanks. -- Regards/Gruss, Boris.
