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: 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 v2 1/1] Documentation/x86: Add the AMX enabling example
Date: Wed, 29 Jun 2022 15:42:35 -0700 [thread overview]
Message-ID: <20220629224235.20589-2-chang.seok.bae@intel.com> (raw)
In-Reply-To: <20220629224235.20589-1-chang.seok.bae@intel.com>
Explain steps to enable the dynamic feature with a code example.
Signed-off-by: Chang S. Bae <chang.seok.bae@intel.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Changes from v1:
* Update the description without mentioning CPUID & XGETBV (Dave Hansen).
---
Documentation/x86/xstate.rst | 42 ++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/Documentation/x86/xstate.rst b/Documentation/x86/xstate.rst
index 5cec7fb558d6..c439901419fb 100644
--- a/Documentation/x86/xstate.rst
+++ b/Documentation/x86/xstate.rst
@@ -64,6 +64,48 @@ the handler allocates a larger xstate buffer for the task so the large
state can be context switched. In the unlikely cases that the allocation
fails, the kernel sends SIGSEGV.
+AMX TILE_DATA enabling example
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The following steps dynamically enable TILE_DATA:
+
+ 1. An application first needs to determine the feature support::
+
+ #include <asm/prctl.h>
+ #include <sys/syscall.h>
+ #include <stdio.h>
+ #include <unistd.h>
+
+ #define ARCH_GET_XCOMP_SUPP 0x1021
+
+ #define XFEATURE_XTILECFG 17
+ #define XFEATURE_XTILEDATA 18
+ #define XFEATURE_MASK_XTILE ((1 << XFEATURE_XTILECFG) | (1 << XFEATURE_XTILEDATA))
+
+ unsigned long features;
+ long rc;
+
+ ...
+
+ rc = syscall(SYS_arch_prctl, ARCH_GET_XCOMP_SUPP, &features);
+
+ if (!rc && (features & XFEATURE_MASK_XTILE) == XFEATURE_MASK_XTILE)
+ printf("AMX is available.\n");
+
+ 2. After determining support for AMX, an application must explicitly ask
+ permission to use it::
+
+ #define ARCH_REQ_XCOMP_PERM 0x1023
+
+ ...
+
+ rc = syscall(SYS_arch_prctl, ARCH_REQ_XCOMP_PERM, XFEATURE_XTILEDATA);
+
+ if (!rc)
+ printf("AMX is ready for use.\n");
+
+Note this example does not include the sigaltstack preparation.
+
Dynamic features in signal frames
---------------------------------
--
2.17.1
next prev parent reply other threads:[~2022-06-29 22:51 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 ` Chang S. Bae [this message]
2022-06-29 23:30 ` [PATCH v2 1/1] Documentation/x86: Add the AMX enabling example Luck, Tony
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=20220629224235.20589-2-chang.seok.bae@intel.com \
--to=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 \
--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®