From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: <linux-kernel@vger.kernel.org>,
<linux-tip-commits@vger.kernel.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>
Cc: Tony Luck <tony.luck@intel.com>, <x86@kernel.org>
Subject: Re: [tip: x86/fpu] x86/arch_prctl: Add AMX feature numbers as ABI constants
Date: Wed, 22 Mar 2023 15:02:04 -0700 [thread overview]
Message-ID: <ffeee8d3-3b92-fe21-1b5e-1c17444a6a8b@intel.com> (raw)
In-Reply-To: <167951609395.5837.17233221474519558802.tip-bot2@tip-bot2>
On 3/22/2023 1:14 PM, tip-bot2 for Chang S. Bae wrote:
> The following commit has been merged into the x86/fpu branch of tip:
>
> x86/arch_prctl: Add AMX feature numbers as ABI constants
>
> Each distinct XSAVE feature has a number assigned to it. Among other
> things, the number determines the ordering of features in the XSAVE
> buffer and is also used to generate XSAVE bitmasks like the value
> for XCR0.
>
> AMX state is dynamically enabled by the architecture-specific prctl().
> This prctl() takes one XSAVE feature number as an argument. However, the
> feature numbers are not defined in any readily available userspace headers.
> The means that each userspace app trying to use dynamic feature prctl()s
> will likely end up defining their own constants for each feature.
>
> Since these feature numbers are a part of the uabi, expose them in the
> prctl() uabi header. Save everyone the trouble of looking them up and
> defining their own.
>
> [ dhansen: expand changelog a bit ]
Sorry, it looks like I was not diligent enough to explain what those
numbers are and that they are now part of the ABI.
Thank you for the write-up.
Chang
prev parent reply other threads:[~2023-03-22 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 20:14 tip-bot2 for Chang S. Bae
2023-03-22 22:02 ` Chang S. Bae [this message]
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=ffeee8d3-3b92-fe21-1b5e-1c17444a6a8b@intel.com \
--to=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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®