On 2018-02-04, Patrick Wildt <patr...@blueri.se> wrote: >> this diff allows us to load the Intel microcode much earlier.
I'm trying to understand the twisty logic here. There are three cases: (1) old rev < update rev => update gets applied (2) old rev == update rev => cpu_ucode_intel_match() returns success => "microcode already up-to-date" (3) old rev > update rev => cpu_ucode_intel_match() returns failure => "no microcode update found" Is the different code path for (2) and (3) intentional? Admittedly this is cosmetic. I currently have machines that are in state (3), which is why I noticed. -- Christian "naddy" Weisgerber na...@mips.inka.de