From: "Luck, Tony" <tony.luck@intel.com>
To: "Bae, Chang Seok" <chang.seok.bae@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 1/1] Documentation/x86: Add the AMX enabling example
Date: Wed, 29 Jun 2022 23:30:16 +0000 [thread overview]
Message-ID: <f01bb09a504240059a79a94c24ba4eba@intel.com> (raw)
In-Reply-To: <20220629224235.20589-2-chang.seok.bae@intel.com>
+ #define ARCH_GET_XCOMP_SUPP 0x1021
+
+ #define XFEATURE_XTILECFG 17
+ #define XFEATURE_XTILEDATA 18
What's the long-term plan for these #defines? I see that ARCH_GET_XCOMP_SUPP
is in arch/x86/include/uapi/asm/prctl.h ... so eventually that will show up in distribution
/usr/include/asm/prctl.h courtesy of a glibc update.
But the XFEATURE bits aren't in a "uapi" file. They are an "enum" in:
arch/x86/include/asm/fpu/types.h
How will that get to /usr/include?
-Tony
next prev parent reply other threads:[~2022-06-29 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 22:42 [PATCH v2 0/1] Documentation/x86: Update the dynamic XSTATE doc Chang S. Bae
2022-06-29 22:42 ` [PATCH v2 1/1] Documentation/x86: Add the AMX enabling example Chang S. Bae
2022-06-29 23:30 ` Luck, Tony [this message]
2022-06-30 15:26 ` Chang S. Bae
2022-06-30 16:07 ` Luck, Tony
2022-06-30 16:17 ` Chang S. Bae
2022-06-30 3:03 ` Bagas Sanjaya
2022-06-30 15:38 ` Chang S. Bae
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=f01bb09a504240059a79a94c24ba4eba@intel.com \
--to=tony.luck@intel.com \
--cc=chang.seok.bae@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=reinette.chatre@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox