mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol@kernel.org>
To: Borislav Petkov <bp@alien8.de>, 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: Sun, 1 Nov 2026 12:27:54 +0100	[thread overview]
Message-ID: <bfaee19b-355c-4ada-b1d9-f95b4f1fe272@kernel.org> (raw)
In-Reply-To: <20261031214351.GCauZhF1l6ENBfLKIS@fat_crate.local>

On 31/10/2026 at 22:43, Borislav Petkov wrote:
> 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.

PROCESSOR_SELECT was introduced in 2008 by commit 8d02c2110b3f ("x86:
configuration options to compile out x86 CPU support code"). At that
time, it was gated by CONFIG_EMBEDDED with space savings given as the
main motivation. In the thread [1], Bodo pointed out that this wasn't
specific to embedded systems but his comment didn't get any replies.

Commit 6a108a14fa35 ("kconfig: rename CONFIG_EMBEDDED to
CONFIG_EXPERT") then did a treewide renaming. The commit explains that
EMBEDDED already covered nonstandard configurations beyond embedded
systems but does not give a PROCESSOR_SELECT-specific rationale.

Beyond Bodo's unanswered comment, I did not find further discussion of
the relevance of PROCESSOR_SELECT for non-embedded machines or the
Kconfig user experience. The main point I am raising in this series is
how easily users should be able to disable all the features specific
to CPU vendors they do not need. I think this aspect deserves further
discussion.

Finally, the size savings have changed since 2008. As reported in my
tests, an AMD-only build reduces vmlinux.o size by 8.88%. What used to
be a micro-optimization back then now has a much bigger impact.

[1] https://lore.kernel.org/all/E1KRp7q-0001pd-61@be1.7eggert.dyndns.org/


Yours sincerely,
Vincent Mailhol

      reply	other threads:[~2026-11-01 11:27 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 ` [PATCH 0/3] x86: Make processor vendor selection available without EXPERT Borislav Petkov
2026-11-01 11:27   ` Vincent Mailhol [this message]

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=bfaee19b-355c-4ada-b1d9-f95b4f1fe272@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®