From: Borislav Petkov <bp@alien8.de>
To: Ashok Raj <ashok.raj@intel.com>
Cc: "Ashok Raj" <ashok_raj@linux.intel.com>,
"X86 ML" <x86@kernel.org>, "Andrew Cooper" <amc96@srcf.net>,
LKML <linux-kernel@vger.kernel.org>,
"Ștefan Talpalaru" <stefantalpalaru@yahoo.com>
Subject: Re: [PATCH] x86/microcode/AMD: Attempt applying on every logical thread
Date: Wed, 17 Aug 2022 23:56:02 +0200 [thread overview]
Message-ID: <Yv1j8v7o3lOniUoH@zn.tnic> (raw)
In-Reply-To: <Yv1WXxcIXSQ7nMji@araj-dh-work>
On Wed, Aug 17, 2022 at 08:58:07PM +0000, Ashok Raj wrote:
> For this specific patch in question, its not for testing though.. Its
> required for functional purposes?
From its commit message:
"However, there are microcode patches which do per-thread modification,
see Link tag below.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216211"
TL;DR - the application needs to happen on *every* logical CPU.
> In effect you can test applying the same microcode over and over again
> without having any special patches.
Right now, you cannot downgrade on Zen but apparently applying the same
patch over and over again works.
The patch cache still has a version check and that prevents it but
that's ugly.
I need to test how it behaves on older families first and then think
about how to do this right. Maybe use cpuinfo_x86.microcode to record
what has been applied until now...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-08-17 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 12:00 [PATCH] x86/microcode/AMD: Attempt applying on every logical thread Borislav Petkov
2022-08-16 9:00 ` Ashok Raj
2022-08-16 12:41 ` Borislav Petkov
2022-08-16 16:51 ` Ashok Raj
2022-08-17 12:12 ` Ashok Raj
2022-08-17 14:23 ` Borislav Petkov
2022-08-17 15:29 ` Ashok Raj
2022-08-17 18:13 ` Borislav Petkov
2022-08-17 20:58 ` Ashok Raj
2022-08-17 21:56 ` Borislav Petkov [this message]
2022-08-18 9:58 ` Ashok Raj
2022-11-05 3:45 ` Ashok Raj
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=Yv1j8v7o3lOniUoH@zn.tnic \
--to=bp@alien8.de \
--cc=amc96@srcf.net \
--cc=ashok.raj@intel.com \
--cc=ashok_raj@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefantalpalaru@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.