Hi Jeff, Thomas,
Le Wednesday 05 June 2013 à 19:40 -0400, Jeff Mahoney a écrit :
On 6/5/13 7:37 PM, Thomas Renninger wrote:
On Wednesday, June 05, 2013 06:29:53 PM Jean Delvare wrote:
* I think microcode could be unloaded after use,
Hm, could this be done inside the module already? microcode driver could always return a negative value in its init function whether it could load a firmware file or not. (unless microcode.keep=1 is passed if one wants to examine something)
This would avoid: modprobe microcode rmmod microcode userspace control and possible race conditions. Does this make sense?
Oh, I thought user-space had to do something for the CPU microcode to actually get updated. Or has it changed and just loading the module triggers the update now? Yep, that changed. Intel per CPU family-model-stepping split up files are here: /lib/firmware/intel-ucode and AMD here: /lib/firmware/amd-ucode and this is fetched via firmware loader instead of a tiny binary pushing
On Thursday, June 06, 2013 08:55:56 AM Jean Delvare wrote: things through /dev/cpu/microcode. The latter is deprecated for some time: CONFIG_MICROCODE_OLD_INTERFACE=y This even changed from SLES 11 SP2 -> SP3. Factory microcode_ctl package still needs some cleanup. Anyway, keeping this one as a module is a good idea. Thomas -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org