mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
	Dave Hansen <dave.hansen@intel.com>, <x86@kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	"Sean Christopherson" <seanjc@google.com>,
	Tony Luck <tony.luck@intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/cpufeatures: Free up unused feature bits
Date: Thu, 7 Nov 2024 16:35:59 -0800	[thread overview]
Message-ID: <5a42aca9-ff38-4fb5-8eb2-a43262c8c630@intel.com> (raw)
In-Reply-To: <74338393-4F39-4A04-83B1-BA64CE2D2FDA@zytor.com>

On 11/7/2024 3:49 PM, H. Peter Anvin wrote:
>>> -	if (c->x86 == 6)
>>> -		set_cpu_cap(c, X86_FEATURE_P3);
>>
> 
> Be careful - these bits are used in module strings and so modutils need to understand them.

Sorry, I didn't understand this properly. How do I figure out whether
these bits are used elsewhere? Can you please provide a pointer?

Sohil

  reply	other threads:[~2024-11-08  0:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 23:30 Sohil Mehta
2024-11-07 23:36 ` Dave Hansen
2024-11-07 23:44   ` Sohil Mehta
2024-11-07 23:49     ` H. Peter Anvin
2024-11-08  0:35       ` Sohil Mehta [this message]
2024-11-08  0:37         ` H. Peter Anvin
2024-11-08  1:12       ` Dave Hansen
2024-11-08  2:17         ` Sohil Mehta
2024-11-08 15:31           ` H. Peter Anvin
2024-11-08 18:42         ` Dave Hansen
2024-11-08 18:42         ` Sohil Mehta
2024-11-08 18:46           ` Dave Hansen

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=5a42aca9-ff38-4fb5-8eb2-a43262c8c630@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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®