On Wednesday, December 14, 2011 05:30:56 AM Cristian Rodríguez wrote:
On 05/12/11 00:18, Andi Kleen wrote:
I already have a branch started with the new approach, but not everything tested&together yet. Hopefully soon.
Great, thanks for your efforts, I have a few suggestions if you don't mind to ease our usecases ;-)
- The microcode driver (intel,amd variants) should do nothing when we are running in virtualized environment, just return. It's not that easy. Linux running as Dom0 can and should trigger a microcode update, when running in DomU it should not.
In kvm typically a non-existent CPU is emulated and the microcode driver will not be tried to get loaded. But you can pass kvm -cpu host and then kvm will pass the original CPU cpuid info to the virtualized client which will try to load the microcode driver then. I hope this condition is correctly detected and handled (return -ENODEV?) in the microcode update driver and we can get rid of all additional userspace quirks which try to detect when the microcode driver should get loaded. Above cases need testing as soon as we have CPU autoloading and udev rules in place. Thomas -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org