linux-kernel - Re: [PATCH 1/2] x86/microcode/AMD: Load late on both threads too

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALMp9eR1Ub78MZwdZn178d4OXPu3Au=faBgVGe6ty6ARV+nK8g@mail.gmail.com>
Date:   Wed, 16 Aug 2023 14:23:52 -0700
From:   Jim Mattson <jmattson@...gle.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     dave.hansen@...el.com, linux-kernel@...r.kernel.org,
        stable@...nel.org, x86@...nel.org
Subject: Re: [PATCH 1/2] x86/microcode/AMD: Load late on both threads too

On Wed, Aug 16, 2023 at 2:18 PM Borislav Petkov <bp@...en8.de> wrote:
>
> On Wed, Aug 16, 2023 at 01:17:00PM -0700, Jim Mattson wrote:
> > Is there any way to tell that a microcode patch has been loaded on
> > only one thread?
>
> Only the example you see in the bugzilla link above.
>
> > And what does this mean for SEV-SNP attestation?
>
> More specifically? The CPUID page or microcode revision?

Specifically, "Security Version Numbers (SVNs) of the currently
executing platform firmware and microcode."

> --
> Regards/Gruss,
>     Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette