On Saturday 30 Apr 2016 10:05:40 Jonathan Callen wrote: > The proper way to load microcode into the kernel is now to have it be > part of an initramfs (the initramfs doesn't (I think) have to actually > do anything, just have the microcode firmware in the appropriate > location). This is because some things in userspace (like glibc itself) > only check once for certain CPU features at startup, and newer microcode > will actually disable some of those features on some CPUs (because they > are completely broken anyway). This means that loading the microcode > before any userspace programs run will ensure that applications like > /sbin/init won't crash just because a feature they thought they could > use suddenly disappeared.
Still, it would be better if all kernel versions behaved the same way in this respect. -- Rgds Peter
