The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org,
	"tip-bot2 for H. Peter Anvin (Intel)" <tip-bot2@linutronix.de>,
	linux-tip-commits@vger.kernel.org,
	"Xin Li (Intel)" <xin@zytor.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	x86@kernel.org
Subject: Re: [tip: x86/cpu] x86/cpufeatures: Add {REQUIRED,DISABLED} feature configs
Date: Mon, 10 Mar 2025 19:57:14 +0100	[thread overview]
Message-ID: <Z882Cj2sO5wDWZIs@gmail.com> (raw)
In-Reply-To: <A0C784F1-EF4F-4CCC-98AE-954197CD7554@zytor.com>


* H. Peter Anvin <hpa@zytor.com> wrote:

> >+config X86_DISABLED_FEATURE_FRED
> >+	def_bool y
> >+	depends on !X86_FRED
> >+
> >+config X86_DISABLED_FEATURE_SEV_SNP
> >+	def_bool y
> >+	depends on !KVM_AMD_SEV
> >+
> >+config X86_DISABLED_FEATURE_INVLPGB
> >+	def_bool y
> >+	depends on !BROADCAST_TLB_FLUSH
> 
> I think it is worth noting that the list here was intentionally 
> unchanged from the previous definitions, but that several of these 
> could and probably should be overhauled.

Yeah, note that this list was *not* unchanged since the -v1 submission, 
there's two new dependencies we added since -v1 which ended with the 
FRED entry:

 - X86_DISABLED_FEATURE_INVLPGB dependency we added today, which is due 
   to a new feature freshly merged into tip:x86/mm.

 - X86_DISABLED_FEATURE_SEV_SNP was added a bit back - that too is a 
   fresh sub-feature.

So we are aware, but we are also limited by what we notice. :-)

> For example, CPUID is actually required by any i586+ configuration.

Mind sending patches for anything you can think of? This series is now 
headed for v6.15 via tip:x86/cpu, modulo any unexpected catastrophes in 
-next testing.

Thanks,

	Ingo

  parent reply	other threads:[~2025-03-10 18:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  8:23 [PATCH v6 0/5] x86/cpufeatures: Automatically generate required and disabled feature masks Xin Li (Intel)
2025-02-28  8:23 ` [PATCH v6 1/5] x86/cpufeatures: Rename X86_CMPXCHG64 to X86_CX8 Xin Li (Intel)
2025-02-28 16:53   ` [tip: x86/cpu] " tip-bot2 for H. Peter Anvin (Intel)
2025-02-28  8:23 ` [PATCH v6 2/5] x86/cpufeatures: Add {required,disabled} feature configs Xin Li (Intel)
2025-02-28 16:53   ` [tip: x86/cpu] " tip-bot2 for H. Peter Anvin (Intel)
2025-03-10  8:18   ` [tip: x86/cpu] x86/cpufeatures: Add {REQUIRED,DISABLED} " tip-bot2 for H. Peter Anvin (Intel)
2025-03-10 14:43     ` H. Peter Anvin
2025-03-10 15:06       ` Borislav Petkov
2025-03-10 18:57       ` Ingo Molnar [this message]
2025-03-19 11:04   ` [tip: x86/core] " tip-bot2 for H. Peter Anvin (Intel)
2025-02-28  8:23 ` [PATCH v6 3/5] x86/cpufeatures: Generate a feature mask header based on build config Xin Li (Intel)
2025-02-28 16:53   ` [tip: x86/cpu] " tip-bot2 for H. Peter Anvin (Intel)
2025-03-03 11:38   ` [PATCH v6 3/5] " Aithal, Srikanth
2025-03-03 12:05     ` H. Peter Anvin
2025-03-03 13:25       ` Borislav Petkov
2025-03-03 22:34         ` H. Peter Anvin
2025-03-04 10:18         ` Xin Li
2025-03-04 10:29           ` Borislav Petkov
2025-03-05  7:30             ` Xin Li
2025-03-05 22:04               ` Borislav Petkov
2025-03-22 19:58                 ` Xin Li
2025-02-28  8:23 ` [PATCH v6 4/5] x86/cpufeatures: Remove {disabled,required}-features.h Xin Li (Intel)
2025-02-28 16:53   ` [tip: x86/cpu] " tip-bot2 for Xin Li (Intel)
2025-02-28  8:23 ` [PATCH v6 5/5] x86/cpufeatures: Use AWK to generate {REQUIRED|DISABLED}_MASK_BIT_SET Xin Li (Intel)
2025-02-28 16:53   ` [tip: x86/cpu] " tip-bot2 for Xin Li (Intel)
2025-03-10  8:18   ` [tip: x86/cpu] x86/cpufeatures: Use AWK to generate {REQUIRED|DISABLED}_MASK_BIT_SET in <asm/cpufeaturemasks.h> tip-bot2 for Xin Li (Intel)
2025-03-19 11:03   ` [tip: x86/core] " tip-bot2 for Xin Li (Intel)
2025-02-28  9:26 ` [PATCH v6 0/5] x86/cpufeatures: Automatically generate required and disabled feature masks Ingo Molnar

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=Z882Cj2sO5wDWZIs@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=tip-bot2@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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