From: Sohil Mehta <sohil.mehta@intel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>, <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>,
Dave Hansen <dave.hansen@intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
<linux-kernel@vger.kernel.org>, <stable@kernel.org>
Subject: Re: [PATCH 1/2] x86/microcode/intel: Refresh the revisions that determine old_microcode
Date: Tue, 19 Aug 2025 09:13:27 -0700 [thread overview]
Message-ID: <cbd74335-055d-46e5-9dc3-9197ff95cebf@intel.com> (raw)
In-Reply-To: <0bfc7329-e13b-4781-a331-9f8898110b5f@citrix.com>
On 8/19/2025 4:18 AM, Andrew Cooper wrote:
> On 19/08/2025 6:19 am, Pawan Gupta wrote:
>> On Mon, Aug 18, 2025 at 12:01:36PM -0700, Sohil Mehta wrote:
>>> Update the minimum expected revisions of Intel microcode based on the
>>> microcode-20250512 (May 2025) release.
>>>
>>> Cc: <stable@kernel.org> # v6.15+
>>> Signed-off-by: Sohil Mehta <sohil.mehta@intel.com>
>>> ---
>>> .../kernel/cpu/microcode/intel-ucode-defs.h | 86 +++++++++++--------
>>> 1 file changed, 48 insertions(+), 38 deletions(-)
>>>
>> ".model = 0x55, .steppings = 0x0040" is being removed? Total number of
>> entries in the table are being reduced by ~10.
>
Based on the diff stat, aren't the total entries increasing by 10?
> That's because early in a CPUs lifecycle, microcode for the late
> pre-production steppings are still included in the public repo, but
> eventually dropped.
>
> Alas, these deletions are documented as well as everything else is in
> the changelog...
>
I sorted the file by FMS to make it easier to spot changes going
forward. Though, I don't think we can rely on the kernel history to
track the microcode changes. Because there isn't a direct 1:1 mapping
between the microcode releases and the kernel update. (Unless that's
what you are proposing)
Dave's initial commit used the Nov 2024 release, and this one is based
on May 2025. There could potentially be multiple releases in the middle
that added and removed stuff which would go unnoticed. Though, using the
script in patch 2 it should be easy to track that (outside the kernel)
if really needed.
> ~Andrew
next prev parent reply other threads:[~2025-08-19 16:13 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 [this message]
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
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=cbd74335-055d-46e5-9dc3-9197ff95cebf@intel.com \
--to=sohil.mehta@intel.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=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=stable@kernel.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 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.