From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>, Sohil Mehta <sohil.mehta@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 11:31:40 -0700 [thread overview]
Message-ID: <4d5a17d5-f26a-4682-ab7b-5a3b05b5af3a@intel.com> (raw)
In-Reply-To: <20250822182447.GHaKi176wVuSsNMmi4@fat_crate.local>
On 8/22/25 11:24, Borislav Petkov wrote:
> Update to the header needs to happen in very controlled manner, when you have
> released tested microcode and have decided to deprecate old microcode.
Right. It'll happen in response to a public microcode release.
> So, actually, this script should NOT be in the kernel but in some repo
> internal in Intel.
We could definitely put it there. But it's generating a 100%
Linux-specific header that nobody else can use. So it's really a purely
Linux thing. Not really a great fit for what is otherwise just a
microcode repository.
I honestly don't care that much if it's in the kernel tree or not. The
best part for me of having it in the kernel is that it makes it easier
for _anybody_ to just go make a patch to update the header when I'm too
lazy to do it.
I'll probably just go stick it in some other kernel.org repo if folks
don't want it upstream.
next prev parent reply other threads:[~2025-08-22 18:31 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 [this message]
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
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=4d5a17d5-f26a-4682-ab7b-5a3b05b5af3a@intel.com \
--to=dave.hansen@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--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=sohil.mehta@intel.com \
--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®