> Q: What prevents a CPU coming up -during- an MTRR change once the rest
> of the cpu hot plugging is present ?
"The force". The more I think about mtrr.c and hotplug, the more I
regret having eaten lunch today. I'm not convinced it will do the right
thing at all with hotplug. init_secondary_cpu() does no frobbing of
the MSRs. For this we relied upon that IPI from cpu #0, which we never
saw. Ugh. horrid.
So possible issues are..
1. cpu #0 sets MSRs, then sets off an IPI. cpu #n isn't 'plugged' yet,
so we miss the IPI and new processors don't get the MSRs poked,
but get their 'state' set so it appears to be ok, but isn't.
2. init on secondary cpu's probably needs to wait until the boot CPU mtrr
code is in a 'known safe' state before it does the magickal
'sync based on whats in cpu #0'
3. What happens when cpu #0 has finished poking registers, and then sets
off an IPI to resync the others, when cpu #n hasn't gotten as far in the
boot sequence to handle that IPI correctly yet ?
Dave.
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/