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

From: Henrique de Moraes Holschuh
Date: Wed Jun 20 2012 - 20:06:30 EST


On Wed, 20 Jun 2012, H. Peter Anvin wrote:
> On 06/20/2012 04:46 PM, Henrique de Moraes Holschuh wrote:
> > Well, it makes the kernel tell us what (amd/intel/whatever) firmware it
> > wants, and requires (after patching) a simple echo 1 >foo to activate. It
> > is also harmless if activated without updated firmware in place.
> >
> > /dev/cpu/microcode requires special software (or a dd with bs>=file size),
> > since it borks if userspace breaks a microcode into two write() syscalls,
> > and requires detection of the cpu vendor. Very annoying.
> >
>
> Yeah, because dd is such an exotic piece of software...

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.

I'll take the firmware interface we already have to support to get
anything done with a lot of other drivers anyway, thank you very much.

--
"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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/