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? This module's modinfo looks very crappy, this should be cleaned up as well.
From a purely technical perspective, yes. We'd need to change the module loader to not treat whatever error code it would return as something other than an error though.
Well, either way we must keep the driver modular, and that's all I care about right now. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org