From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: x86-cpuid@lists.linux.dev, Borislav Petkov <bp@alien8.de>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Sohil Mehta <sohil.mehta@intel.com>,
John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] x86-cpuid-db: Release v2.0
Date: Tue, 8 Oct 2024 15:31:10 +0200 [thread overview]
Message-ID: <ZwU0HtmCTj2rF2T8@lx-t490> (raw)
Hi,
I'm happy to announce release 2.0 of the x86-cpuid-db project:
https://gitlab.com/x86-cpuid.org/x86-cpuid-db
https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/releases/v2.0
Changelog v2.0
--------------
- Introduce a new transformer, which generates one Linux kernel C header
file for all the cpuid leaves' bitfields.
(A single linux kernel C header file, with version tag on top, shall be
easier to maintain than multiple headers; Linux x86 PQ pending)
- Introduce the cpuidgen --kheaders option to invoke that transformer.
- Extend the cpuid database bitfields coverage:
- Add Transmeta vendor tags to the appropriate bitfields at leaves
0x0, 0x01, and from leaves 0x80000000 to 0x80000006.
- Add the Transmeta-specific CPUID leaves 0x03, and 0x80860000 to
0x80860007.
- Add Centaur/Zhaoxin leaves 0xc0000000 and 0xc0000001, along with
Zhoaxin's exclusive feature bits.
- Add some documentation in the schema for the <linux> annotation tag.
CPUID bitfields coverage
~~~~~~~~~~~~~~~~~~~~~~~~
In total, this release increases the x86-cpuid database bitfield
coverage to:
CPUID leaves: 63 leaves
CPUID bitfields: 907 entries
Changes to generated files styling
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Beside the new cpuid leaves and bitfields, the generated Linux kernel C
structures has changed from:
/*
* CPUID leaf 0
*/
struct leaf0_sl0 {
...;
};
/*
* CPUID leaf 7
*/
struct leaf7_sl0 {
...;
};
struct leaf7_sl1 {
...;
};
to:
/*
* Leaf 0x0
* Maximum standard leaf number + CPU vendor string
*/
struct leaf_0x0_0 {
...;
};
/*
* Leaf 0x7
* Extended CPU features enumeration
*/
struct leaf_0x7_0 {
...;
};
struct leaf_0x7_1 {
...;
};
Overall, this removes ambiguity for IDs like 0x16, and improves kernel
code greppability (x86 PQ pending).
Finally, the generated CSV and C header files can be quickly checked in
full from the release artifacts at:
https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/releases/v2.0
Thanks,
--
Ahmed S. Darwish
Linutronix GmbH
next reply other threads:[~2024-10-08 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 13:31 Ahmed S. Darwish [this message]
2024-10-08 13:38 ` Andrew Cooper
2024-10-08 15:44 ` 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=ZwU0HtmCTj2rF2T8@lx-t490 \
--to=darwi@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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®