mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
To: "Ahmed S. Darwish" <darwi@linutronix.de>
Cc: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Sean Christopherson <seanjc@google.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Christian Ludloff <ludloff@gmail.com>,
	Sohil Mehta <sohil.mehta@intel.com>,
	John Ogness <john.ogness@linutronix.de>,
	x86@kernel.org, x86-cpuid@lists.linux.dev,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 00/90] x86: Introduce a centralized CPUID data model
Date: Tue, 14 Apr 2026 15:10:52 +0000	[thread overview]
Message-ID: <ad5VAT5fModtt6w3@wieczorr-mobl1.localdomain> (raw)

On 2026-04-13 at 16:38:31 +0200, Ahmed S. Darwish wrote:
>Hi Maciej,
>
>On Tue, 07 Apr 2026, Maciej Wieczor-Retman wrote:
>>
>> Hi, very cool rework! So far I didn't notice any problems while testing.
>>
>
>Thanks a lot for testing!
>
>I will appreciate then adding a Tested-by tag on v7, where the interesting
>bits will hopefully start to get merged.

Sure, I'll rememeber to retest once v7 is out :)

>>
>> Buy anyway I wanted to ask if you thought about including the cpuid_deps[] or
>> cpuid_dependent_features[] into the new cpuid API ecosystem?
>>
>> Or if not (since this patchset is quite long already :b ), then do you have any
>> idea where best it could fit in? During discussion on [1] you mentioned the
>> feature depenedency should be encoded in x86-cpuid-db. I assume you meant it
>> would need to be first patched into there, then parsed by Kconfig?
>>
>> [1] https://lore.kernel.org/all/acruJf-pyld-fTh1@lx-t490/
>>
>
>Sorry, I'm just back from Easter vacations; that's why I didn't answer your
>question in that other thread.
>
>x86-cpuid-db will encode all the feature dependencies in its XML database.
>Then it can generate all the necessary dependency structures, in a way that
>is easy to parse for all kernel phases; including the kconfig build phase.
>
>Then, what you want to do can be cleanly added on top.
>
>P.S. I'm already removing <asm/cpufeatures.h> in the next iteration, along
>with its ugly "/proc/cpuinfo names inside multi-line C comments" hack.

Cool, thanks for letting me know!

>
>Kind regards,
>Ahmed

-- 
Kind regards
Maciej Wieczór-Retman


             reply	other threads:[~2026-04-14 15:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 15:10 Maciej Wieczor-Retman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-07  8:55 Maciej Wieczor-Retman
2026-04-07  8:59 ` Borislav Petkov
2026-03-27  2:15 Ahmed S. Darwish
2026-03-27 15:23 ` Borislav Petkov
2026-03-30 18:29   ` Ahmed S. Darwish
2026-03-30 23:08     ` Borislav Petkov
2026-04-13 14:03       ` Ahmed S. Darwish
2026-04-27 18:45         ` Ahmed S. Darwish
2026-05-05 13:33           ` Borislav Petkov
2026-05-05 15:12             ` Borislav Petkov
2026-05-05 19:11               ` Christian Ludloff
2026-05-06  8:50                 ` Borislav Petkov
2026-05-06 13:59                   ` H. Peter Anvin
2026-05-06 14:58                     ` Borislav Petkov
2026-05-06 18:13                   ` Christian Ludloff
2026-05-06 21:57                 ` Ahmed S. Darwish
2026-05-06 22:18                   ` Borislav Petkov
2026-05-06 23:03                     ` Christian Ludloff
2026-05-06 20:52               ` Ahmed S. Darwish
2026-05-07 10:17                 ` Borislav Petkov
2026-05-07 20:02                   ` Ahmed S. Darwish
2026-04-07 10:09 ` Maciej Wieczor-Retman
2026-04-13 14:38   ` Ahmed S. Darwish
2026-04-21 17:27 ` Maciej Wieczor-Retman
2026-04-29 10:09   ` Ahmed S. Darwish

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=ad5VAT5fModtt6w3@wieczorr-mobl1.localdomain \
    --to=m.wieczorretman@pm.me \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=darwi@linutronix.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludloff@gmail.com \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86-cpuid@lists.linux.dev \
    --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®