Re: [PATCH] x86, microcode: Make reload interface per system

Henrique de Moraes Holschuh
2012-06-21T02:33:32Z

On Wed, 20 Jun 2012, H. Peter Anvin wrote:
> On 06/20/2012 05:06 PM, Henrique de Moraes Holschuh wrote:
> > No, because dd if=<whatever> of=/dev/cpu/microcode bs=1M means I have to
> > add dd to the initramfs or to busybox, AND it will break the day the
> > microcode data file gets bigger than 1M. And it will be at best very
> > annoying to have to special case each vendor to locate the correct
> > microcode, etc.
>
> No.
>
> The whole point is you won't have to put ANYTHING in your initramfs,
> period. The early microcode blob will be all you need there.

Yes. And the sooner it gets done that way, the better. But until then, IMO
the firmware_request + sysfs trigger interface is easier and friendler to
use than /dev/cpu/microcode.

> So the only issue left is what to do when you want to update the
> microcode in an already running system.

Well, IMO the firmware interface makes that somewhat easier on the userland
side, as it is more userfriendly from a generic support for processor
microcode updates point-of-view. And the sysfs trigger isn't that horrible,
it is certainly easier to script than an ioctl or syscall.

I guess it's better if we just agree to disagree on this...

--
"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