Re: [PATCH v6 00/90] x86: Introduce a centralized CPUID data model

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