From: Sohil Mehta <sohil.mehta@intel.com>
To: <x86-cpuid@lists.linux.dev>, "Ahmed S . Darwish" <darwi@linutronix.de>
Cc: 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: Mon, 23 Sep 2024 15:57:11 -0700 [thread overview]
Message-ID: <70cf05c3-0ba6-4a5e-a7ab-21cadad3c255@intel.com> (raw)
In-Reply-To: <20240923223213.852758-1-sohil.mehta@intel.com>
Hi Ahmed,
On 9/23/2024 3:32 PM, Sohil Mehta wrote:
> + <bit20 len="1" id="nmi_src" desc="NMI-source reporting with FRED event data" />
I am starting to work on a new x86 feature and submitting this in
preparation for that.
> <bit21 len="1" id="amx_fp16" desc="AMX-FP16: FP16 tile operations">
> <linux feature="true" proc="false" />
I couldn't find much documentation for the <linux> tag. When is it
expected to be included?
Also, are the following linux hint attributes documented somewhere? I
couldn't decipher them from their name itself.
> <xs:complexType name="linuxType">
> <xs:attribute type="xs:boolean" name="feature" use="required" />
> <xs:attribute type="xs:boolean" name="proc" use="required" />
> <xs:attribute type="xs:string" name="altid" use="optional" />
> <xs:attribute type="xs:string" name="procid" use="optional" />
> </xs:complexType>
>
Does feature="true" mean the feature is intended for linux or it is
merged into the linux kernel?
Thanks,
Sohil
next prev parent reply other threads:[~2024-09-23 22:57 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 [this message]
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
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=70cf05c3-0ba6-4a5e-a7ab-21cadad3c255@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.