From: Borislav Petkov <bp@alien8.de>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, pawel.chmielewski@linux.intel.com,
Farrah Chen <farrah.chen@intel.com>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] x86/cpu: Clear feature bits disabled at compile-time
Date: Fri, 13 Feb 2026 01:58:13 +0100 [thread overview]
Message-ID: <20260213005813.GGaY53JfOLNoSJNgRe@fat_crate.local> (raw)
In-Reply-To: <57039edb-419c-4e4a-96d0-3578e233b594@intel.com>
On Thu, Feb 12, 2026 at 04:14:07PM -0800, Sohil Mehta wrote:
> So, as of today, if one of these features shows up, a user can't be sure
> whether the kernel has enabled it or not. Right?
This is not such a critical bug - judging by how no one noticed it until
now...
> My suggestion is that:
> Instead of (or maybe along with) fixing this buggy interface, would it
> be better to put this information in something like debugfs/sysfs? So,
> at least new user software can start using that.
... to go and make big waves and "fix" everything. We'll address this
inconsistency eventually and go on with our lives.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-02-13 0:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 15:33 [PATCH v5 0/3] x86: Capability bits fix and required bits sanity check Maciej Wieczor-Retman
2026-02-12 15:34 ` [PATCH v5 1/3] x86/cpu: Clear feature bits disabled at compile-time Maciej Wieczor-Retman
2026-02-12 15:58 ` Borislav Petkov
2026-02-12 16:23 ` Maciej Wieczor-Retman
2026-02-12 21:34 ` H. Peter Anvin
2026-02-12 21:51 ` Borislav Petkov
2026-02-12 23:04 ` Sohil Mehta
2026-02-12 23:47 ` Borislav Petkov
2026-02-13 0:14 ` Sohil Mehta
2026-02-13 0:36 ` Sohil Mehta
2026-02-13 0:58 ` Borislav Petkov [this message]
2026-02-13 20:11 ` H. Peter Anvin
2026-02-12 15:35 ` [PATCH v5 2/3] x86/cpu: Check if feature string is non-zero Maciej Wieczor-Retman
2026-02-13 0:28 ` Sohil Mehta
2026-02-13 10:02 ` Maciej Wieczor-Retman
2026-02-13 18:22 ` Sohil Mehta
2026-02-13 19:10 ` Maciej Wieczor-Retman
2026-02-13 20:00 ` Sohil Mehta
2026-02-13 20:26 ` Maciej Wieczor-Retman
2026-02-13 20:15 ` H. Peter Anvin
2026-02-13 20:24 ` Maciej Wieczor-Retman
2026-02-12 15:35 ` [PATCH v5 3/3] x86/cpu: Required feature bits sanity check Maciej Wieczor-Retman
2026-02-13 20:17 ` H. Peter Anvin
2026-02-13 20:23 ` [PATCH v5 0/3] x86: Capability bits fix and required " H. Peter Anvin
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=20260213005813.GGaY53JfOLNoSJNgRe@fat_crate.local \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=farrah.chen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.wieczorretman@pm.me \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@redhat.com \
--cc=pawel.chmielewski@linux.intel.com \
--cc=sohil.mehta@intel.com \
--cc=stable@vger.kernel.org \
--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®