From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Sohil Mehta <sohil.mehta@intel.com>,
x86-cpuid@lists.linux.dev, Thomas Gleixner <tglx@linutronix.de>,
Xin Li <xin@zytor.com>
Subject: Re: [PATCH] db: Add Intel NMI-source reporting feature flag
Date: Sat, 28 Sep 2024 09:34:55 +0200 [thread overview]
Message-ID: <Zvexn9PPCmX0WEYw@lx-t490> (raw)
In-Reply-To: <6CFCC415-2F08-465D-B61B-E465A44DDD67@zytor.com>
Hi hpa,
On Fri, 27 Sep 2024, H. Peter Anvin wrote:
>
> Should we include a copy of this database in the kernel sources?
>
We expclitily didn't want it to make it a linux kernel build dependency.
Mainly out of a desire to use the database for other projects beside the
kernel as well, starting with Xen.
So, the tool have multiple transformers which generates "listings". One
of these listings is now merged:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/arch/x86/kcpuid/cpuid.csv
The tool also generates Linux kernel C data structures:
https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/jobs/7907817537/artifacts/download
We're working on a patch series for the x86 subsystem, where the above
data structures will be integrated in the kernel -- along with cpuid
accessors and a data model.
All geneated files also has tags on top that will allow KernelCI to
verify the integrity of these CSV or C header-file listings:
"Tagging Conventions for Generated Files"
https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/blob/tip/README.rst
(I was going to show this and other things at Plumbers x86 track demo,
but sadly, BBB screen sharing misbehaved during the talk... Next time
I'll have a proper fallback mechanism.)
Thanks,
--
Ahmed S. Darwish
Linutronix GmbH
next prev parent reply other threads:[~2024-09-28 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 22:32 [PATCH] db: Add Intel NMI-source reporting feature flag Sohil Mehta
2024-09-23 22:57 ` Sohil Mehta
2024-09-26 13:12 ` Ahmed S. Darwish
2024-09-26 15:33 ` Andrew Cooper
2024-09-26 19:57 ` Ahmed S. Darwish
2024-09-27 17:47 ` Sohil Mehta
2024-09-27 18:29 ` H. Peter Anvin
2024-09-27 18:55 ` Sohil Mehta
2024-09-28 7:34 ` Ahmed S. Darwish [this message]
2024-09-24 16: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=Zvexn9PPCmX0WEYw@lx-t490 \
--to=darwi@linutronix.de \
--cc=hpa@zytor.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=x86-cpuid@lists.linux.dev \
--cc=xin@zytor.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.