From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/fpu for 6.4
Date: Thu, 27 Apr 2023 09:10:10 -0700 [thread overview]
Message-ID: <20230427161010.1053561-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/fpu changes for 6.4. There's no _actual_ kernel
functionality here. This expands the documentation around AMX support
including some code examples. The example code also exposed the fact
that hardware architecture constants as part of the ABI, but there's
no easy place that they get defined for apps. Adding them to a uabi
header will eventually make life easier for consumers of the ABI.
--
The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:
Linux 6.3-rc3 (2023-03-19 13:27:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_fpu_for_6.4
for you to fetch changes up to 5fbff260755750559aa12a30f6fa7f8a863666f1:
Documentation/x86: Explain the state component permission for guests (2023-03-22 13:08:02 -0700)
----------------------------------------------------------------
* Improve AMX documentation along with example code
* Explicitly make some hardware constants part of the uabi
----------------------------------------------------------------
Chang S. Bae (4):
Documentation/x86: Explain the purpose for dynamic features
x86/arch_prctl: Add AMX feature numbers as ABI constants
Documentation/x86: Add the AMX enabling example
Documentation/x86: Explain the state component permission for guests
Documentation/x86/xstate.rst | 100 ++++++++++++++++++++++++++++++++++++++
arch/x86/include/uapi/asm/prctl.h | 3 ++
2 files changed, 103 insertions(+)
next reply other threads:[~2023-04-27 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 16:10 Dave Hansen [this message]
2023-04-28 17:23 ` [GIT PULL] x86/fpu for 6.4 pr-tracker-bot
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=20230427161010.1053561-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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