From: Jim Mattson <jmattson@google.com>
To: dave.hansen@intel.com
Cc: bp@alien8.de, linux-kernel@vger.kernel.org, stable@kernel.org,
x86@kernel.org, Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH 1/2] x86/microcode/AMD: Load late on both threads too
Date: Wed, 16 Aug 2023 13:17:00 -0700 [thread overview]
Message-ID: <20230816201700.589822-1-jmattson@google.com> (raw)
In-Reply-To: <12a12721-239b-457e-1ff7-f98c02cb7abe@intel.com>
On Wed, Jun 07, 2023 at 13:15:42 -0700, Dave Hansen wrote:
>On 6/7/23 13:03, Borislav Petkov wrote:
>> On Wed, Jun 07, 2023 at 12:36:53PM -0700, Dave Hansen wrote:
>>> What's the benefit of doing the loading on both threads? I would have
>>> naively thought it was just wasted work.
>> I have the perfect example for this, see:
>>
>> e7ad18d1169c ("x86/microcode/AMD: Apply the patch early on every logical thread")
>>
>> so it is for reasons like that.
>
>Yikes, so the second CMT thread reports a bumped version but not all the
>_effects_ of that version? That's, uh ... fun???
That does seem like fun. :)
Borislav,
Is there any way to tell that a microcode patch has been loaded on only one
thread? And what does this mean for SEV-SNP attestation?
next prev parent reply other threads:[~2023-08-16 20:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 14:13 [PATCH 1/2] x86/microcode/AMD: Load late on both threads too Borislav Petkov
2023-06-05 14:13 ` [PATCH 2/2] x86/microcode: Add a "microcode=" command line option Borislav Petkov
2023-06-08 1:55 ` Ashok Raj
2023-06-09 12:28 ` Borislav Petkov
2023-06-09 15:37 ` Ashok Raj
2023-06-12 9:06 ` Borislav Petkov
2023-06-12 9:20 ` [tip: x86/microcode] " tip-bot2 for Borislav Petkov (AMD)
2023-06-12 15:26 ` [PATCH 2/2] " Thomas Gleixner
2023-06-12 15:42 ` Borislav Petkov
2023-06-12 16:04 ` Borislav Petkov
2023-06-12 17:23 ` Thomas Gleixner
2023-06-13 8:32 ` Borislav Petkov
2023-06-07 19:36 ` [PATCH 1/2] x86/microcode/AMD: Load late on both threads too Dave Hansen
2023-06-07 20:03 ` Borislav Petkov
2023-06-07 20:15 ` Dave Hansen
2023-08-16 20:17 ` Jim Mattson [this message]
2023-08-16 21:18 ` Borislav Petkov
2023-08-16 21:23 ` Jim Mattson
2023-08-16 21:30 ` Borislav Petkov
2023-08-16 21:36 ` Jim Mattson
2023-08-16 21:58 ` Borislav Petkov
2023-08-16 22:37 ` Jim Mattson
2023-08-17 15:40 ` Borislav Petkov
2023-08-17 18:02 ` Peter Shier
2023-08-18 8:43 ` Borislav Petkov
2023-06-12 9:20 ` [tip: x86/microcode] " tip-bot2 for Borislav Petkov (AMD)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230816201700.589822-1-jmattson@google.com \
--to=jmattson@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).