From: Sohil Mehta <sohil.mehta@intel.com>
To: Dave Hansen <dave.hansen@intel.com>, Jon Kohler <jon@nutanix.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
Alex Murray <alex.murray@canonical.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Old microcode CPU matching issue - x86/microcode/intel: Refresh the revisions that determine old_microcode
Date: Fri, 21 Nov 2025 12:26:54 -0800 [thread overview]
Message-ID: <86580b33-8ab2-4fb9-9166-77e751a20944@intel.com> (raw)
In-Reply-To: <20e43176-f7e6-40aa-86f1-d709269b4787@intel.com>
On 11/20/2025 4:39 PM, Dave Hansen wrote:
> Any additional testing or eyeballs on the code would be appreciated.
I tried out the updated patches on an SPR system. With some made up
entries the old_microcode flagging worked as expected.
next prev parent reply other threads:[~2025-11-21 20:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 19:01 [PATCH 0/2] x86/intel: Refresh the old ucode revisions with a script Sohil Mehta
2025-08-18 19:01 ` [PATCH 1/2] x86/microcode/intel: Refresh the revisions that determine old_microcode Sohil Mehta
2025-08-19 5:19 ` Pawan Gupta
2025-08-19 11:18 ` Andrew Cooper
2025-08-19 16:13 ` Sohil Mehta
2025-08-19 18:31 ` Pawan Gupta
2025-08-19 18:28 ` Pawan Gupta
2025-08-19 19:07 ` Dave Hansen
2025-08-19 20:21 ` Andrew Cooper
2025-10-22 17:14 ` Old microcode CPU matching issue - " Jon Kohler
2025-10-22 17:53 ` Dave Hansen
2025-11-14 20:34 ` Dave Hansen
2025-11-20 16:35 ` Jon Kohler
2025-11-20 17:29 ` Sohil Mehta
2025-11-20 19:13 ` Sohil Mehta
2025-11-20 19:27 ` Dave Hansen
2025-11-21 0:39 ` Dave Hansen
2025-11-21 20:26 ` Sohil Mehta [this message]
2025-11-26 3:00 ` Jon Kohler
2025-08-18 19:01 ` [PATCH 2/2] scripts/x86: Add a script to update minimum Intel ucode revisions Sohil Mehta
2025-08-19 17:14 ` Dave Hansen
2025-08-19 20:41 ` Sohil Mehta
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=86580b33-8ab2-4fb9-9166-77e751a20944@intel.com \
--to=sohil.mehta@intel.com \
--cc=alex.murray@canonical.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jon@nutanix.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®