On Saturday 30 Apr 2016 17:50:44 Neil Bothwick wrote: > On 30 April 2016 16:02:49 BST, Peter Humphrey <pe...@prh.myzen.co.uk> > wrote: > > 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. > > Not if the newer way is better, which appears to be the case here.
My results show the behaviour alternating between versions, not simply progressing from the old to the new. You'd be right of course in the latter case. -- Rgds Peter
