On Thu, 25 Sep 2014, Borislav Petkov wrote:
> On Thu, Sep 25, 2014 at 12:30:06PM -0300, Henrique de Moraes Holschuh wrote:
> > Userspace can install the microcode only inside the initramfs, if it wants
> > to avoid it being loaded later. It is not even too difficult to do so.
>
> Hmm, so in thinking about this more, what we need to do on all kernels
> should be something along those lines (if I'm not missing something,
> that is):
>
>
> if (early microcode loading support) {
> install microcode into initramfs;
> }
>
> install microcode into /lib/firmware/...;
> tell the user to reboot;
>
> On the next reboot, everything gets loaded automatically.
>
> Of course, user needs to make sure that the microcode loader module gets
> loaded during boot. If its built-in, we're fine.
We still need to update x86_capability after a microcode update for the
above to really work in the "install microcode into initramfs" case.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
