From: Måns Rullgård
Date: Tue Jan 19 2016 - 07:29:55 EST

Ingo Molnar <mingo@xxxxxxxxxx> writes:

> So can we do something more intelligent instead, such as modifying the
> Kconfigs in a way that it's not possible to have CONFIG_MICROCODE
> enabled while BLK_DEV_INITRD is disabled?

The problem with *any* approach involving Kconfig is that it still
leaves users free to load microcode whenever they want, even if they're
not supposed to. Doing so apparently works correctly (almost) every
time (how does it fail if it does?), and no warnings are issued to
suggest it might be a bad idea. Force-enabling BLK_DEV_INITRD isn't
going to make anyone change their boot scripts. Many might not even
notice that it got silently enabled. So what purpose does it serve to
play games with the config when it has no actual impact on the usage of
the driver?

I'd also like to get a coherent answer to why microcode update is
preferably done from an initrd as opposed to shortly after mounting a
regular disk. My systems seem perfectly happy doing the latter.

Måns Rullgård