From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: make config X86_FEATURE_NAMES visible with EXPERT
Date: Tue, 9 May 2023 11:43:12 -0700 [thread overview]
Message-ID: <c0dcbda3-e131-2460-4c61-e98d0be750ff@intel.com> (raw)
In-Reply-To: <20230509184135.GDZFqT3yC/j5bJA1l5@fat_crate.local>
On 5/9/23 11:41, Borislav Petkov wrote:
> On Tue, May 09, 2023 at 11:38:27AM -0700, Dave Hansen wrote:
>> This actually isn't _great_ for x86. We hid X86_FEATURE_NAMES behind
>> EMBEDDED because we didn't want to see it 99% of the time. But just
>> about everyone uses EXPERT=y, so the end result here is that everyone
>> will now see X86_FEATURE_NAMES.
>>
>> Oh well. It's just one Kconfig option. Not a big deal.
> Or we can make it unconditional. I haven't heard anything from the tiny
> .config folks in a while and a !X86_FEATURE_NAMES kernel is just
> unfriendly.
Like remove the option entirely? Or just remove the prompt so folks
have to hack the .config for it?
next prev parent reply other threads:[~2023-05-09 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 8:40 [PATCH] x86: make config X86_FEATURE_NAMES visible with EXPERT Lukas Bulwahn
2023-05-09 14:07 ` Dave Hansen
2023-05-09 18:20 ` Lukas Bulwahn
2023-05-09 18:38 ` Dave Hansen
2023-05-09 18:41 ` Borislav Petkov
2023-05-09 18:43 ` Dave Hansen [this message]
2023-05-09 19:03 ` Borislav Petkov
2023-05-10 7:01 ` Lukas Bulwahn
2023-05-10 7:46 ` Lukas Bulwahn
2023-05-10 1:07 ` H. Peter Anvin
2023-05-10 7:51 ` 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=c0dcbda3-e131-2460-4c61-e98d0be750ff@intel.com \
--to=dave.hansen@intel.com \
--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=lukas.bulwahn@gmail.com \
--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