d in mind for early boot.
What would be the downside of a microcode cache?
I didn't follow the whole flow of how the CPUs get to their microcode patches,
but I thought the mc_saved* stuff did caching of the microcode, since
scan_microcode, the only user of load_builtin_intel_microcode, is on
itrd
Microcode can be baked into the kernel image via CONFIG_EXTRA_FIRMWARE
and the early loader supports that, but still depended on
BLK_DEV_INITRD.
This dependency is removed.
Signed-off-by: Alexander Hirsch <1ze...@gmail.com>
---
arch/x86/Kconfig| 2 +-
arch
Microcode can be baked into the kernel image via CONFIG_EXTRA_FIRMWARE
and the early loader supports that, but still depended on
BLK_DEV_INITRD.
This dependency is removed.
Signed-off-by: Alexander Hirsch <1ze...@gmail.com>
---
This patch depends on the "Parse built-in microcode earl
3 matches
Mail list logo