From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: dave.hansen@intel.com, len.brown@intel.com, tony.luck@intel.com,
rafael.j.wysocki@intel.com, reinette.chatre@intel.com,
dan.j.williams@intel.com
Cc: bagasdotme@gmail.com, corbet@lwn.net, linux-doc@vger.kernel.org,
linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
chang.seok.bae@intel.com
Subject: [PATCH v3 1/2] x86/arch_prctl: Add AMX feature numbers as ABI constants
Date: Mon, 11 Jul 2022 10:13:46 -0700 [thread overview]
Message-ID: <20220711171347.27309-2-chang.seok.bae@intel.com> (raw)
In-Reply-To: <20220711171347.27309-1-chang.seok.bae@intel.com>
AMX state is dynamically enabled by the architecture-specific prctl().
Expose the XSTATE numbers as ABI constants. It will help applications as no
more spec look-up is needed for these numbers.
Signed-off-by: Chang S. Bae <chang.seok.bae@intel.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org
---
Changes from v2:
* Add as a new patch (Tony Luck).
---
arch/x86/include/uapi/asm/prctl.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/include/uapi/asm/prctl.h b/arch/x86/include/uapi/asm/prctl.h
index 500b96e71f18..f298c778f856 100644
--- a/arch/x86/include/uapi/asm/prctl.h
+++ b/arch/x86/include/uapi/asm/prctl.h
@@ -16,6 +16,9 @@
#define ARCH_GET_XCOMP_GUEST_PERM 0x1024
#define ARCH_REQ_XCOMP_GUEST_PERM 0x1025
+#define ARCH_XCOMP_TILECFG 17
+#define ARCH_XCOMP_TILEDATA 18
+
#define ARCH_MAP_VDSO_X32 0x2001
#define ARCH_MAP_VDSO_32 0x2002
#define ARCH_MAP_VDSO_64 0x2003
--
2.17.1
next prev parent reply other threads:[~2022-07-11 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 17:13 [PATCH v3 0/2] x86: AMX enabling example with new constants Chang S. Bae
2022-07-11 17:13 ` Chang S. Bae [this message]
2022-07-11 17:13 ` [PATCH v3 2/2] Documentation/x86: Add the AMX enabling example Chang S. Bae
2022-07-21 20:53 ` [PATCH v3 0/2] x86: AMX enabling example with new constants Luck, Tony
2022-07-21 20:57 ` 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=20220711171347.27309-2-chang.seok.bae@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bagasdotme@gmail.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 \
--cc=tony.luck@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
all inboxes | Powered by JetHome®