From: Dave Hansen <dave.hansen@intel.com>
To: Xin Li <xin@zytor.com>,
Wieczor-Retman Maciej <maciej.wieczor-retman@intel.com>
Cc: Gleixner Thomas <tglx@linutronix.de>,
Molnar Ingo <mingo@redhat.com>, Petkov Borislav <bp@alien8.de>,
Hansen Dave <dave.hansen@linux.intel.com>,
x86@kernel.org, "Anvin H. Peter" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Clear LAM and FRED feature bits
Date: Tue, 22 Jul 2025 07:11:47 -0700 [thread overview]
Message-ID: <0390b5e0-f32d-400b-b2e3-b1c9cf162c69@intel.com> (raw)
In-Reply-To: <32382f60-79fb-4cfa-87b4-581f92c980da@zytor.com>
On 7/22/25 02:08, Xin Li wrote:
>> + /*
>> + * If a feature is disabled during compile time clear its feature
>> + * bit to prevent it from showing up in the x86_capability bitmask.
>> + */
>> + if (!cpu_feature_enabled(X86_FEATURE_LAM))
>> + setup_clear_cpu_cap(X86_FEATURE_LAM);
>> +
>> + if (!cpu_feature_enabled(X86_FEATURE_FRED))
>> + setup_clear_cpu_cap(X86_FEATURE_FRED);
>> +
>
> The following code will work as a generic fix:
>
> c->x86_capability[i] &= ~DISABLED_MASK(i);
>
> And DISABLED_MASK(x) needs to be defined like DISABLED_MASK_BIT_SET(x).
Maciej, I would much rather have a generic fix than force everyone to
remember to open-code this for every new feature that gets disabled.
next prev parent reply other threads:[~2025-07-22 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 7:44 Maciej Wieczor-Retman
2025-07-22 9:08 ` Xin Li
2025-07-22 14:11 ` Dave Hansen [this message]
2025-07-22 15:43 ` Maciej Wieczor-Retman
2025-07-22 15:31 ` Maciej Wieczor-Retman
2025-07-22 16:46 ` H. Peter Anvin
2025-07-22 17:22 ` Xin Li
2025-07-22 18:19 ` Maciej Wieczor-Retman
2025-07-22 19:26 ` 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=0390b5e0-f32d-400b-b2e3-b1c9cf162c69@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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®