From: Alex Murray <alex.murray@canonical.com>
To: Dave Hansen <dave.hansen@linux.intel.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, bp@alien8.de,
andrew.cooper3@citrix.com,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] [v4] x86/cpu: Help users notice when running old Intel microcode
Date: Fri, 07 Feb 2025 12:17:48 +1030 [thread overview]
Message-ID: <87tt96ikzf.fsf@canonical.com> (raw)
In-Reply-To: <20250206214723.B5F4DB81@davehans-spike.ostc.intel.com>
Hey Dave,
On Thu, 2025-02-06 at 13:47:23 -0800, Dave Hansen wrote:
>
> Also note that the "intel-ucode-defs.h" file is simple, ugly and
> has lots of magic numbers. That's on purpose and should allow a
> single file to be shared across lots of stable kernel regardless of if
> they have the new "VFM" infrastructure or not. It was generated with
> a dumb script.
>
Should this script be included as part of this patch so that it is easy
for others to update intel-ucode-defs.h if needed in the future?
Thanks,
Alex
next prev parent reply other threads:[~2025-02-07 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 21:47 [PATCH] [v4] x86/cpu: Help users notice when running old Intel microcode Dave Hansen
2025-02-07 1:47 ` Alex Murray [this message]
2025-02-07 5:04 ` Dave Hansen
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=87tt96ikzf.fsf@canonical.com \
--to=alex.murray@canonical.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox