From: Vincent Mailhol <mailhol@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Vincent Mailhol <mailhol@kernel.org>
Subject: [PATCH v2 0/2] x86: Add CPU vendor dependencies for MCE and legacy
Date: Fri, 13 Nov 2026 18:59:56 +0100 [thread overview]
Message-ID: <20261113-processor_select_is_not_an_expert_feature-v2-0-ae630b1f2e28@kernel.org> (raw)
Intel-style MCE features and legacy AMD NUMA detection remain available
when support for their CPU vendors is disabled. Add the corresponding
CPU_SUP_* dependencies so that these options are only available when
support for the relevant vendors is enabled.
Signed-off-by: Vincent Mailhol <mailhol@kernel.org>
---
Changes in v2:
- Drop patch 3, which removed PROCESSOR_SELECT's EXPERT dependency.
Update the cover letter to reflect the reduced scope.
- Update the Intel MCE prompt and help text to mention Zhaoxin.
Link to v1: https://patch.msgid.link/20261031-processor_select_is_not_an_expert_feature-v1-0-6227bdbbe5a9@kernel.org
---
Vincent Mailhol (2):
x86/mce: Add CPU_SUP_* dependencies for Intel/Zhaoxin MCE features
x86/numa: Add CPU_SUP_AMD dependency for legacy AMD NUMA
arch/x86/Kconfig | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
---
base-commit: 7e1392a42ea288d70a266f6553fe06f57f8647ea
change-id: 20261030-processor_select_is_not_an_expert_feature-4f329d352ec3
Best regards,
--
Vincent Mailhol <mailhol@kernel.org>
next reply other threads:[~2026-11-13 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 17:59 Vincent Mailhol [this message]
2026-11-13 17:59 ` [PATCH v2 1/2] x86/mce: Add CPU_SUP_* dependencies for Intel/Zhaoxin MCE features Vincent Mailhol
2026-11-13 17:59 ` [PATCH v2 2/2] x86/numa: Add CPU_SUP_AMD dependency for legacy AMD NUMA Vincent Mailhol
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=20261113-processor_select_is_not_an_expert_feature-v2-0-ae630b1f2e28@kernel.org \
--to=mailhol@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@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®