On Tue, 31 Jul 2012, Philipp Kern wrote: > On Mon, Jul 30, 2012 at 08:22:00PM -0300, Henrique de Moraes Holschuh wrote: > > > 2. fixed per-core (errors in every core but the BSP, and updates every > > > core > > > at once) -- should be in -stable soon enough. > > > > The "fixed per-core ABI" makes the kernel refuse the reload command on every > > core but the BSP, and changes the behaviour of a reload command to the BSP > > to "reload every core". The BSP was chosen, because that's the one core you > > are not allowed to offline. > > What happens in multi socket systems? If all cores of a secondary processor > are > offline, will the kernel just do a firmware load when one of them gets > reactivated?
Yes, provided you don't "rmmod microcode". > > That said, during boot these sysfs interfaces are only used when running a > > custom-built kernel with a built-in microcode driver. The Debian kernel > > doesn't need it, as a system-wide reload is triggered when the microcode > > module is loaded by the initramfs. > > Well, it's also done in the postinst. Yes, it is. Were it not safe to do in the postinst, we couldn't do it anywhere (i.e. it would not be safe to do it at all). > I unblocked amd64-microcode nevertheless. Thank you. I will request an unblock of iucode-tool and intel-microcode after they cook for a little while more in unstable. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
