mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
To: Borislav Petkov <bp@alien8.de>
Cc: dave.hansen@linux.intel.com, hpa@zytor.com, xin@zytor.com,
	chang.seok.bae@intel.com, mingo@redhat.com,
	elena.reshetova@intel.com, maciej.wieczor-retman@intel.com,
	babu.moger@amd.com, sohil.mehta@intel.com,
	pawan.kumar.gupta@linux.intel.com, pmladek@suse.com,
	nik.borisov@suse.com, ptesarik@suse.com, darwi@linutronix.de,
	tglx@kernel.org, peterz@infradead.org, jpoimboe@kernel.org,
	ak@linux.intel.com, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v12 0/4] x86: Capability bits fix and required bits sanity check
Date: Tue, 31 Mar 2026 14:27:25 +0000	[thread overview]
Message-ID: <acvZeeB-M_kNMoB1@wieczorr-mobl1.localdomain> (raw)
In-Reply-To: <20260331140216.GDacvT6IPW1gf003z-@fat_crate.local>

On 2026-03-31 at 16:02:16 +0200, Borislav Petkov wrote:
>On Fri, Mar 27, 2026 at 03:10:39PM +0000, Maciej Wieczor-Retman wrote:
>> Series aims to fix the inconsistency between the cpuinfo behavior and
>> the documentation. Specifically the features that are not compiled are
>> still present in the cpuinfo bitmasks as enabled. This is not in line
>> with the documentation which specifies that not-compiled features are
>> not present in /proc/cpuinfo.
>
>So, I just realized (yah, I am slow).
>
>So Ahmed's patchset
>
>https://lore.kernel.org/all/20260327021645.555257-1-darwi@linutronix.de
>
>already has all the information in order to achieve what this has been trying
>and more. I.e., it has all CPUID bit names and so on.
>
>So I'd suggest we concentrate all our efforts on reviewing Ahmed's pile and if
>then more functionality is needed, we can put it ontop.
>
>Because this is simply duplicating effort and we will end up replacing this
>eventually so it is all wasted effort.
>
>So let's please concentrate all our energy there.
>
>Thx.
>
>--
>Regards/Gruss,
>    Boris.
>
>https://people.kernel.org/tglx/notes-about-netiquette

Okay, I'll stop posting this patchset and go test Ahmed's work.

-- 
Kind regards
Maciej Wieczór-Retman


  reply	other threads:[~2026-03-31 14:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 15:10 Maciej Wieczor-Retman
2026-03-27 15:10 ` [PATCH v12 1/4] x86/cpu: Clear feature bits disabled at compile-time Maciej Wieczor-Retman
2026-03-27 15:10 ` [PATCH v12 2/4] x86/cpu: Check if feature string is non-zero Maciej Wieczor-Retman
2026-03-27 17:50   ` Sohil Mehta
2026-03-27 21:28     ` Maciej Wieczor-Retman
2026-03-30 20:00   ` Borislav Petkov
2026-03-30 20:42     ` Maciej Wieczor-Retman
2026-03-30 21:15       ` Borislav Petkov
2026-03-30 21:44         ` H. Peter Anvin
2026-03-30 22:59           ` Borislav Petkov
2026-03-30 23:42             ` H. Peter Anvin
2026-03-31  2:15               ` H. Peter Anvin
2026-03-31 13:27               ` Borislav Petkov
2026-03-27 15:10 ` [PATCH v12 3/4] x86/cpu: Do a sanity check on required feature bits Maciej Wieczor-Retman
2026-03-27 17:10   ` Pawan Gupta
2026-03-27 17:22     ` Maciej Wieczor-Retman
2026-03-27 15:11 ` [PATCH v12 4/4] x86/cpu: Clear feature bits whose dependencies were cleared Maciej Wieczor-Retman
2026-03-28  2:22   ` H. Peter Anvin
2026-03-30 10:40     ` Maciej Wieczor-Retman
2026-03-30 21:41     ` Ahmed S. Darwish
2026-03-31 11:41       ` Maciej Wieczor-Retman
2026-04-01 15:16       ` Maciej Wieczor-Retman
2026-04-13 14:42         ` Ahmed S. Darwish
2026-03-30  6:11 ` [PATCH v12 0/4] x86: Capability bits fix and required bits sanity check Andi Kleen
2026-03-30  8:52   ` Maciej Wieczor-Retman
2026-03-30 23:40   ` H. Peter Anvin
2026-03-31 14:02 ` Borislav Petkov
2026-03-31 14:27   ` Maciej Wieczor-Retman [this message]
2026-03-31 14:46     ` Borislav Petkov

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=acvZeeB-M_kNMoB1@wieczorr-mobl1.localdomain \
    --to=m.wieczorretman@pm.me \
    --cc=ak@linux.intel.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=darwi@linutronix.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=elena.reshetova@intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=ptesarik@suse.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@kernel.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