From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: x86-cpuid@lists.linux.dev, Borislav Petkov <bp@alien8.de>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
John Ogness <john.ogness@linutronix.de>,
Avadhut Naik <avadhut.naik@amd.com>,
linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] x86-cpuid-db: Release v2.1
Date: Wed, 5 Mar 2025 13:54:30 +0100 [thread overview]
Message-ID: <Z8hJhgGVduJWFqRE@lx-t490> (raw)
Hi,
I'm happy to announce release 2.1 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.1
Changelog v2.1
--------------
- Add spellchecking and x86 terminology style enforcement for all CPUID
bitfield descriptions in the XML database. Build multiple x86
specific hunspell(5) dictionary and affix files for such enforcement.
- Use such logic to standardize the style for x86 trademarks, registers,
opcodes, byte units, hexadecimal digits, and x86 abbreviated and
non-abbreviated technical terms.
- Similarly, refuse abbreviated terms that might be OK in code but not
in official listings (e.g., "addr", "instr", "reg", "virt", etc.)
- Introduce scripts/spellcheck_xml.sh to automate the hunspell
invocation, and add it to the project's CI pipeline.
- Update the CPUID database:
- Leaf 0xd: Apply vendor fixes from Andrew Cooper (Xen / Citrix)
- Leaf 0x80000020/0x80000021: Add new Zen5 SoC bits. Thanks to
Avadhut Naik (AMD).
- Leaf 0x7: Add new NMI source reporting bit. Thanks to Sohil
Mehta (Intel).
- All leaves: Fix all issues identified by the new hunspell(5)
pipeline.
Release coverage
----------------
CPUID leaves: 63 leaves
CPUID bitfields: 918 entries
Artifacts
---------
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.1
Thanks,
--
Ahmed S. Darwish
Linutronix GmbH
reply other threads:[~2025-03-05 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Z8hJhgGVduJWFqRE@lx-t490 \
--to=darwi@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®