From: Jiri Slaby <jirislaby@kernel.org>
To: Dave Hansen <dave.hansen@linux.intel.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, bp@alien8.de,
kan.liang@linux.intel.com
Subject: Re: [v2][PATCH 4/5] x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id'
Date: Wed, 9 Apr 2025 13:13:53 +0200 [thread overview]
Message-ID: <de04dc00-f01d-4c27-a6f8-873398bf8d4a@kernel.org> (raw)
In-Reply-To: <20241213185132.07555E1D@davehans-spike.ostc.intel.com>
I noted this on IRC...
On 13. 12. 24, 19:51, Dave Hansen wrote:
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> The AMD erratum 1386 detection code uses and old style 'x86_cpu_desc'
> table. Replace it with 'x86_cpu_id' so the old style can be removed.
>
> I did not create a new helper macro here. The new table is certainly
> more noisy than the old and it can be improved on. But I was hesitant
> to create a new macro just for a single site that is only two ugly
> lines in the end.
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> ---
>
> b/arch/x86/kernel/cpu/amd.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff -puN arch/x86/kernel/cpu/amd.c~amd-x86_cpu_id arch/x86/kernel/cpu/amd.c
> --- a/arch/x86/kernel/cpu/amd.c~amd-x86_cpu_id 2024-12-13 10:47:55.714076132 -0800
> +++ b/arch/x86/kernel/cpu/amd.c 2024-12-13 10:47:55.718076292 -0800
> @@ -795,10 +795,9 @@ static void init_amd_bd(struct cpuinfo_x
> clear_rdrand_cpuid_bit(c);
> }
>
> -static const struct x86_cpu_desc erratum_1386_microcode[] = {
> - AMD_CPU_DESC(0x17, 0x1, 0x2, 0x0800126e),
> - AMD_CPU_DESC(0x17, 0x31, 0x0, 0x08301052),
> - {},
If I am to tell, the {} is needed, otherwise you touch the array OOB (at
least with the "m->flags & X86_CPU_ID_FLAG_ENTRY_VALID" test -- if the
bit is set in the memory, then much more than that...).
> +static const struct x86_cpu_id erratum_1386_microcode[] = {
> + X86_MATCH_VFM_STEPS(VFM_MAKE(X86_VENDOR_AMD, 0x17, 0x01), 0x2, 0x2, 0x0800126e),
> + X86_MATCH_VFM_STEPS(VFM_MAKE(X86_VENDOR_AMD, 0x17, 0x31), 0x0, 0x0, 0x08301052),
> };
>
> static void fix_erratum_1386(struct cpuinfo_x86 *c)
> @@ -814,7 +813,7 @@ static void fix_erratum_1386(struct cpui
> * Clear the feature flag only on microcode revisions which
> * don't have the fix.
> */
> - if (x86_cpu_has_min_microcode_rev(erratum_1386_microcode))
> + if (x86_match_min_microcode_rev(erratum_1386_microcode))
> return;
>
> clear_cpu_cap(c, X86_FEATURE_XSAVES);
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-04-09 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 18:51 [v2][PATCH 0/5] x86/cpu: Remove duplicate microcode version matching infrastructure Dave Hansen
2024-12-13 18:51 ` [v2][PATCH 1/5] x86/cpu: Introduce new microcode matching helper Dave Hansen
2024-12-13 18:51 ` [v2][PATCH 2/5] x86/cpu: Expose only stepping min/max interface Dave Hansen
2024-12-13 18:51 ` [v2][PATCH 3/5] x86/cpu: Replace PEBS use of 'x86_cpu_desc' use with 'x86_cpu_id' Dave Hansen
2024-12-13 18:51 ` [v2][PATCH 4/5] x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id' Dave Hansen
2025-04-09 11:13 ` Jiri Slaby [this message]
2025-04-09 15:18 ` Borislav Petkov
2025-04-09 15:21 ` Dave Hansen
2025-04-09 15:45 ` Jiri Slaby
2024-12-13 18:51 ` [v2][PATCH 5/5] x86/cpu: Remove 'x86_cpu_desc' infrastructure 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=de04dc00-f01d-4c27-a6f8-873398bf8d4a@kernel.org \
--to=jirislaby@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kan.liang@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