From: Sohil Mehta <sohil.mehta@intel.com>
To: "Ahmed S. Darwish" <darwi@linutronix.de>
Cc: <x86-cpuid@lists.linux.dev>, Thomas Gleixner <tglx@linutronix.de>,
Xin Li <xin@zytor.com>, "H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] db: Add Intel NMI-source reporting feature flag
Date: Fri, 27 Sep 2024 10:47:56 -0700 [thread overview]
Message-ID: <a8fc6ca4-79e3-41f5-b195-e91d4d515f8b@intel.com> (raw)
In-Reply-To: <ZvVdzJIIqaC_javn@lx-t490>
On 9/26/2024 6:12 AM, Ahmed S. Darwish wrote:
>
> The <linux> tag means that this bit is also represented inside the Linux
> Kernel x86 tree in various means.
>
Got it. But this would mean that the entry needs to be submitted after
the linux usage is established.
> For now, the goal was to cover all known names for
> the cpuid feature bits, especially when they differ; i.e. canonical name
> vs. Linux X86_FEATURE name vs. Linux /proc/cpuinfo name.
>
Also, the various cpuid bit usages in the kernel might happen in stages.
Are you planning to have scripts that automatically pull this data from
the kernel as and when these usages get merged? I believe asking
developers to submit multiple edits to the cpuid-db might be
inconvenient and error prone.
> Thanks for the question! I'll indeed need to document that part of the
> schema before the v2.0 release.
>
Thanks! That would be very useful as more folks start contributing to
the project.
-Sohil
next prev parent reply other threads:[~2024-09-27 17:48 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 [this message]
2024-09-27 18:29 ` H. Peter Anvin
2024-09-27 18:55 ` Sohil Mehta
2024-09-28 7:34 ` Ahmed S. Darwish
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=a8fc6ca4-79e3-41f5-b195-e91d4d515f8b@intel.com \
--to=sohil.mehta@intel.com \
--cc=darwi@linutronix.de \
--cc=hpa@zytor.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.