From: "tip-bot2 for Eric Biggers" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Eric Biggers <ebiggers@kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Christoph Hellwig <hch@lst.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/fpu] x86/fpu: Check for missing AVX and AVX-512 xstate bits
Date: Wed, 09 Sep 2026 23:58:04 -0000 [thread overview]
Message-ID: <178899828430.623050.8638024070858129406.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20260901145740.42337-2-ebiggers@kernel.org>
The following commit has been merged into the x86/fpu branch of tip:
Commit-ID: 518aa9948e4f2ba69b7066371d3ac8e4d31d604e
Gitweb: https://git.kernel.org/tip/518aa9948e4f2ba69b7066371d3ac8e4d31d604e
Author: Eric Biggers <ebiggers@kernel.org>
AuthorDate: Tue, 01 Sep 2026 07:57:33 -07:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Wed, 02 Sep 2026 10:35:40 -07:00
x86/fpu: Check for missing AVX and AVX-512 xstate bits
If the CPU declares AVX or AVX-512 support, verify that the corresponding
xstate bits are also set. If not, warn and clear them.
This eliminates the perceived need for AVX and AVX-512 optimized code in the
kernel to call cpu_has_xfeatures(). That has never been universally done,
which strongly suggests that it has never really been needed in practice, but
this should remove any remaining doubt.
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Acked-by: Christoph Hellwig <hch@lst.de>
Link: https://patch.msgid.link/20260901145740.42337-2-ebiggers@kernel.org
---
arch/x86/kernel/fpu/xstate.c | 25 +++++++++++++++++++++++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
index a7b6524..97cfd4f 100644
--- a/arch/x86/kernel/fpu/xstate.c
+++ b/arch/x86/kernel/fpu/xstate.c
@@ -806,7 +806,7 @@ static u64 __init guest_default_mask(void)
void __init fpu__init_system_xstate(unsigned int legacy_size)
{
unsigned int eax, ebx, ecx, edx;
- u64 xfeatures;
+ u64 xfeatures, mask;
int err;
int i;
@@ -818,6 +818,8 @@ void __init fpu__init_system_xstate(unsigned int legacy_size)
if (!boot_cpu_has(X86_FEATURE_XSAVE)) {
pr_info("x86/fpu: x87 FPU will use %s\n",
boot_cpu_has(X86_FEATURE_FXSR) ? "FXSAVE" : "FSAVE");
+ /* Disable all dependent flags too */
+ setup_clear_cpu_cap(X86_FEATURE_XSAVE);
return;
}
@@ -833,7 +835,8 @@ void __init fpu__init_system_xstate(unsigned int legacy_size)
cpuid_count(CPUID_LEAF_XSTATE, 1, &eax, &ebx, &ecx, &edx);
fpu_kernel_cfg.max_features |= ecx + ((u64)edx << 32);
- if ((fpu_kernel_cfg.max_features & XFEATURE_MASK_FPSSE) != XFEATURE_MASK_FPSSE) {
+ mask = XFEATURE_MASK_FPSSE;
+ if ((fpu_kernel_cfg.max_features & mask) != mask) {
/*
* This indicates that something really unexpected happened
* with the enumeration. Disable XSAVE and try to continue
@@ -844,6 +847,24 @@ void __init fpu__init_system_xstate(unsigned int legacy_size)
goto out_disable;
}
+ mask |= XFEATURE_MASK_YMM;
+ if (boot_cpu_has(X86_FEATURE_AVX)) {
+ if ((fpu_kernel_cfg.max_features & mask) != mask) {
+ pr_err(FW_BUG
+ "x86/fpu: Disabling AVX support due to missing xstate features\n");
+ setup_clear_cpu_cap(X86_FEATURE_AVX);
+ }
+ }
+
+ mask |= XFEATURE_MASK_AVX512;
+ if (boot_cpu_has(X86_FEATURE_AVX512F)) {
+ if ((fpu_kernel_cfg.max_features & mask) != mask) {
+ pr_err(FW_BUG
+ "x86/fpu: Disabling AVX-512 support due to missing xstate features\n");
+ setup_clear_cpu_cap(X86_FEATURE_AVX512F);
+ }
+ }
+
if (fpu_kernel_cfg.max_features & XFEATURE_MASK_APX &&
fpu_kernel_cfg.max_features & (XFEATURE_MASK_BNDREGS | XFEATURE_MASK_BNDCSR)) {
/*
next prev parent reply other threads:[~2026-09-09 23:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 14:57 [PATCH v5 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Eric Biggers
2026-09-01 14:57 ` [PATCH v5 1/8] x86/fpu: Check for missing AVX and AVX-512 xstate bits Eric Biggers
2026-09-09 23:58 ` tip-bot2 for Eric Biggers [this message]
2026-09-01 14:57 ` [PATCH v5 2/8] um: " Eric Biggers
2026-09-09 23:58 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 3/8] crypto: x86 - Stop using cpu_has_xfeatures() Eric Biggers
2026-09-09 23:58 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 4/8] lib/crypto: x86: " Eric Biggers
2026-09-09 23:57 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 5/8] lib/crc: " Eric Biggers
2026-09-09 23:57 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 6/8] x86/fpu: Remove cpu_has_xfeatures() Eric Biggers
2026-09-09 23:57 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-10 8:38 ` [PATCH v5 6/8] " Peter Zijlstra
2026-09-10 14:23 ` Borislav Petkov
2026-09-10 14:59 ` Eric Biggers
2026-09-10 15:44 ` Borislav Petkov
2026-09-01 14:57 ` [PATCH v5 7/8] xor: Remove redundant X86_FEATURE_OSXSAVE check Eric Biggers
2026-09-09 23:57 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-10 15:38 ` tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 8/8] xor: Add AVX-512 optimized xor_gen() Eric Biggers
2026-09-09 23:57 ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-10 15:38 ` tip-bot2 for Eric Biggers
2026-09-02 17:11 ` [PATCH v5 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Borislav Petkov
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=178899828430.623050.8638024070858129406.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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®