On Mon, Oct 10, 2011 at 10:29:13PM +0200, Borislav Petkov wrote: > > Hmm... is it possible to tell whether the core coming online is the > > same one as the last time? If that's possible, the problem becomes > > pretty simple and we can simply tell people who are mixing > > suspend/hibernate with physical hotplug that they're crazy. > > It is possible to compare ucode revisions of the core coming online and > what we have in memory and do the update only if it is necessary. We > still can keep the ucode image without the need for revalidation (and > reloading). > > Better? Yeah yeah, I don't know how ucode is matched to specific CPU but just store that identification of the last CPU and on ONLINE if it stays the same, use the existing one. If not, request new one. It shouldn't be difficult && solves the issue at hand while not breaking hot-swap case. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
