Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1;
Date:   Wed, 6 Dec 2023 21:31:58 +0100
From:   Borislav Petkov <bp@alien8.de>
To:     Jann Horn <jannh@google.com>
Cc:     Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        Dave Hansen <dave.hansen@linux.intel.com>, x86@kernel.org,
        "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/microcode: Be more verbose, especially about loading
 errors
Message-ID: <20231206203158.GEZXDaPslvxtOS/gze@fat_crate.local>
References: <20231206172844.1756871-1-jannh@google.com>
 <20231206195814.GDZXDSVgtCWspEJx8Q@fat_crate.local>
 <CAG48ez3weAU-Uti0QyBSDNRv8xYqCJ5UbgJvssEWAWpvyon0DA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAG48ez3weAU-Uti0QyBSDNRv8xYqCJ5UbgJvssEWAWpvyon0DA@mail.gmail.com>
Precedence: bulk

On Wed, Dec 06, 2023 at 09:23:48PM +0100, Jann Horn wrote:
> Well, yes, except that if no microcode blob is loaded, you're not
> gonna have the errata fixes and/or security mitigations that you might
> expect to have.

We say that too:

microcode: Current revision: 0x000000f0
microcode: Updated early from: 0x000000be

That second line would be missing.

And updated microcode != microcode version for all the mitigations is
even available.

Therefore, the mitigation fixes all report that too. Look for
"[Mm]icrocode" in the mitigation strings in arch/x86/kernel/cpu/bugs.c.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette