From: Sohil Mehta <sohil.mehta@intel.com>
To: Borislav Petkov <bp@alien8.de>, Dave Hansen <dave.hansen@intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"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>,
Andrew Cooper <andrew.cooper3@citrix.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scripts/x86/intel: Add a script to update the minimum ucode revisions
Date: Fri, 22 Aug 2025 14:52:33 -0700 [thread overview]
Message-ID: <791d0ed9-27ab-48bb-bacc-8332aba7398b@intel.com> (raw)
In-Reply-To: <20250822192751.GJaKjEtw5Rf4f0K3DE@fat_crate.local>
On 8/22/2025 12:27 PM, Borislav Petkov wrote:
> On Fri, Aug 22, 2025 at 12:16:59PM -0700, Dave Hansen wrote:
>> Ahh, gotcha. Should we slap something like this in the script?
>>
>> This script is intended to be run in response to releases of the
>> official Intel microcode github repository[link]. Typically,
>> someone at Intel would see a new release, run this script,
>> refresh the intel-ucode-defs.h file and send a patch upstream to
>> update the mainline and stable versions.
>
> Yap, thanks!
>
Thanks! Here is the updated help description in the script:
DESCRIPTION = f"""
For Intel CPUs, update the microcode revisions that determine
X86_BUG_OLD_MICROCODE.
This script is intended to be run in response to releases of the
official Intel microcode GitHub repository:
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git
It takes the Intel microcode files as input and uses iucode-tool to
extract the revision information. It prints the output in the format
expected by intel-ucode-defs.h.
Usage:
./{script} /path/to/microcode/files > /path/to/intel-ucode-defs.h
Typically, someone at Intel would see a new release, run this script,
refresh the intel-ucode-defs.h file, and send a patch upstream to update
the mainline and stable versions.
"""
If there are no other comments, I'll send out a revised version with an
updated commit message early next week.
prev parent reply other threads:[~2025-08-22 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 0:44 Sohil Mehta
2025-08-22 10:09 ` Borislav Petkov
2025-08-22 18:03 ` Sohil Mehta
2025-08-22 18:24 ` Borislav Petkov
2025-08-22 18:31 ` Dave Hansen
2025-08-22 19:06 ` Borislav Petkov
2025-08-22 19:16 ` Dave Hansen
2025-08-22 19:27 ` Borislav Petkov
2025-08-22 21:52 ` Sohil Mehta [this message]
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=791d0ed9-27ab-48bb-bacc-8332aba7398b@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=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®