Re: [PATCH v7 004/120] x86/cpuid: Introduce <asm/cpuid/leaf_types.h>
Christian Ludloff <[email protected]> Mon, 8 Jun 2026 14:30:22 -0700
| Newsgroups | dev.linux.lists.x86-cpuid,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAKSQd8W5060knJMy1eQeNCWzAo-A8V3bLqgdRZBgKc-QYT6E5A@mail.gmail.com> |
On Mon, Jun 8, 2026 at 7:49=E2=80=AFAM Borislav Petkov <[email protected]> wrote= : > What you're doing is a database of *all* CPUID leafs. How long until some= one > copies or exports the header to something? Or starts generating the heade= r > from your XML and using it in her/his project? > > And what happens if someone has already started using the headers, you fi= x > those spelling mistakes, release a new revision and someone updates the > generated headers locally and code starts failing to build all of a sudde= n? > > What do you do then? > > I think with issues like that which can cause nasty workarounds, we canno= t be > urgent enough in fixing them. The database will never be perfect =E2=80=93 it is always in catch-up mode in terms of leaves/fields/values that need to be fixed and/or added. That much I can tell you with absolute certainty after more than 30 years of https://www.sandpile.org/x86/cpuid.htm maintenance, and yes, being personally responsible for some of the CPUID madness. Embrace that chase of completeness and correctness =E2=80=93 "perfect is the enemy of good". Ahmed, can you enable gitlab issue tracking? -- C.