From: Borislav Petkov <bp@alien8.de>
To: Vincent Mailhol <mailhol@kernel.org>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86: Make processor vendor selection available without EXPERT
Date: Sat, 31 Oct 2026 14:43:51 -0700 [thread overview]
Message-ID: <20261031214351.GCauZhF1l6ENBfLKIS@fat_crate.local> (raw)
In-Reply-To: <20261031-processor_select_is_not_an_expert_feature-v1-0-6227bdbbe5a9@kernel.org>
On Sat, Oct 31, 2026 at 08:51:48AM +0100, Vincent Mailhol wrote:
> Restricting a kernel build to a known CPU vendor currently requires
> enabling EXPERT.
>
> Make PROCESSOR_SELECT available without EXPERT. It remains disabled by
> default, preserving support for all applicable CPU vendors in existing
> configurations.
What I am not seeing is git archeology about why it is behind EXPERT and
whether that reason is or is not valid anymore.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-10-31 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 7:51 Vincent Mailhol
2026-10-31 7:51 ` [PATCH 1/3] x86/mce: Add CPU_SUP_* dependencies for Intel/Zhaoxin MCE features Vincent Mailhol
2026-10-31 7:51 ` [PATCH 2/3] x86/numa: Add CPU_SUP_AMD dependency for legacy AMD NUMA Vincent Mailhol
2026-10-31 7:51 ` [PATCH 3/3] x86/cpu: don't gate PROCESSOR_SELECT with EXPERT Vincent Mailhol
2026-10-31 13:58 ` Dave Hansen
2026-11-01 11:26 ` Vincent Mailhol
2026-10-31 21:43 ` Borislav Petkov [this message]
2026-11-01 11:27 ` [PATCH 0/3] x86: Make processor vendor selection available without EXPERT 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=20261031214351.GCauZhF1l6ENBfLKIS@fat_crate.local \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@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®