public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	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: Masahiro Yamada <masahiroy@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH 0/2] Reworking configurability of X86_FEATURE_NAMES
Date: Wed, 10 May 2023 08:57:11 +0200	[thread overview]
Message-ID: <20230510065713.10996-1-lukas.bulwahn@gmail.com> (raw)

Dear Dave, dear Boris, dear x86 maintainers,


as follow-up to the discussion on my initial patch on changing the
visibility of X86_FEATURE_NAMES (see Link), here are two patches:

Patch 1 simply makes the minimal one-line change to make X86_FEATURE_NAMES
disappear from the prompt.

Patch 2 is the more radical change to remove the whole config and see which
code would generally be impacted; just as quick exploration.

The diffstat shows we are getting rid of a bit of code throughout arch/x86,
but the change and reduction is not too complex either:

 arch/x86/Kconfig                  | 12 ------------
 arch/x86/Kconfig.cpu              |  2 +-
 arch/x86/boot/Makefile            |  2 --
 arch/x86/boot/cpu.c               | 13 -------------
 arch/x86/include/asm/cpufeature.h |  5 -----
 arch/x86/kernel/cpu/Makefile      |  4 +---
 arch/x86/kernel/cpu/common.c      |  4 ----
 7 files changed, 2 insertions(+), 40 deletions(-)

Probably, you just want to pick patch 1 and wait for any complaints. Or if
you are confident the compliants will not show up, simply apply both.

Otherwise, I will put it on my list to come back in a year or two, and if
there were no complaints till then, provide the updated patch to remove the
X86_FEATURE_NAMES config then.

Link: https://lore.kernel.org/all/20230509084007.24373-1-lukas.bulwahn@gmail.com/

Best regards,

Lukas


Lukas Bulwahn (2):
  x86: make X86_FEATURE_NAMES non-configurable in prompt
  x86: always build with X86_FEATURE_NAMES functionality

 arch/x86/Kconfig                  | 12 ------------
 arch/x86/Kconfig.cpu              |  2 +-
 arch/x86/boot/Makefile            |  2 --
 arch/x86/boot/cpu.c               | 13 -------------
 arch/x86/include/asm/cpufeature.h |  5 -----
 arch/x86/kernel/cpu/Makefile      |  4 +---
 arch/x86/kernel/cpu/common.c      |  4 ----
 7 files changed, 2 insertions(+), 40 deletions(-)

-- 
2.17.1


             reply	other threads:[~2023-05-10  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10  6:57 Lukas Bulwahn [this message]
2023-05-10  6:57 ` [PATCH 1/2] x86: make X86_FEATURE_NAMES non-configurable in prompt Lukas Bulwahn
2023-05-10  6:57 ` [PATCH 2/2] x86: always build with X86_FEATURE_NAMES functionality Lukas Bulwahn
2023-05-15 21:43   ` [tip: x86/cpu] x86/cpu: Remove X86_FEATURE_NAMES tip-bot2 for Lukas Bulwahn

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=20230510065713.10996-1-lukas.bulwahn@gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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