From: sashiko-bot@kernel.org
To: "Jim Mattson" <jmattson@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] x86/cpufeatures: Make AVX512_BMM depend on AVX512F
Date: Wed, 15 Jul 2026 22:56:00 +0000 [thread overview]
Message-ID: <20260715225600.CB2C81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715224030.3772948-1-jmattson@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Build failure due to undeclared identifier X86_FEATURE_AVX512_BMM.
--
--- Patch [1]: [PATCH] x86/cpufeatures: Make AVX512_BMM depend on AVX512F ---
commit 5ec2859f67a824ceedb01518734f6afb9a711eef
Author: Jim Mattson <jmattson@google.com>
x86/cpufeatures: Make AVX512_BMM depend on AVX512F
This commit explicitly declares a CPUID dependency for AVX512_BMM on
AVX512F so that disabling AVX512F automatically clears AVX512_BMM.
> diff --git a/arch/x86/kernel/cpu/cpuid-deps.c b/arch/x86/kernel/cpu/cpuid-deps.c
> index 146f6f8b0650b..e2e3d0a3abcd5 100644
> --- a/arch/x86/kernel/cpu/cpuid-deps.c
> +++ b/arch/x86/kernel/cpu/cpuid-deps.c
> @@ -75,6 +75,7 @@ static const struct cpuid_dep cpuid_deps[] = {
> { X86_FEATURE_SDCIAE, X86_FEATURE_CAT_L3 },
> { X86_FEATURE_AVX512_BF16, X86_FEATURE_AVX512VL },
> { X86_FEATURE_AVX512_FP16, X86_FEATURE_AVX512BW },
> + { X86_FEATURE_AVX512_BMM, X86_FEATURE_AVX512F },
[Severity: Low]
Is X86_FEATURE_AVX512_BMM defined anywhere in the tree? It appears this
macro is undeclared, which will cause a build failure when compiling
arch/x86/kernel/cpu/cpuid-deps.c.
> { X86_FEATURE_ENQCMD, X86_FEATURE_XSAVES },
> { X86_FEATURE_PER_THREAD_MBA, X86_FEATURE_MBA },
> { X86_FEATURE_SGX_LC, X86_FEATURE_SGX },
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715224030.3772948-1-jmattson@google.com?part=1
next prev parent reply other threads:[~2026-07-15 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 22:40 [PATCH] x86/cpufeatures: Make AVX512_BMM depend on AVX512F Jim Mattson
2026-07-15 22:56 ` sashiko-bot [this message]
2026-07-16 8:08 ` Nikunj A. Dadhania
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=20260715225600.CB2C81F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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