From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: dave.hansen@linux.intel.com, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de
Cc: hpa@zytor.com, corbet@lwn.net, bagasdotme@gmail.com,
tony.luck@intel.com, yang.zhong@intel.com,
linux-doc@vger.kernel.org, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org, chang.seok.bae@intel.com
Subject: [PATCH v5 RESEND 0/4] Documentation/x86: Improve the AMX documentation
Date: Fri, 20 Jan 2023 16:18:56 -0800 [thread overview]
Message-ID: <20230121001900.14900-1-chang.seok.bae@intel.com> (raw)
In-Reply-To: <20220922195810.23248-1-chang.seok.bae@intel.com>
Hi,
This is a resend of the previous posting [1]. They are rebased on the
current tip master.
Looks like the below changes are still helpful for users as I had to
reference the pending series to some folks:
(1) The AMX-enabling code example is expected to clarify the steps.
(2) Along with that, a couple of ABI constants may be useful for users.
(3) Also, describing the motivation will provide the context of this.
(4) Lastly, the description of new guest options is added as missing.
If they are acceptable, I will follow up on the arch_prctl(2) documentation
[2] to update based on this.
These patches can be also found in this repository:
git://github.com/intel/amx-linux.git amx-doc
And the compiled preview is available here:
https://htmlpreview.github.io/?https://github.com/intel/amx-linux/doc-web/x86/xstate.html
Thanks,
Chang
[1] https://lore.kernel.org/lkml/20220922195810.23248-1-chang.seok.bae@intel.com/
[2] arch_prctl(2): https://man7.org/linux/man-pages/man2/arch_prctl.2.html
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(+)
base-commit: 1642cea9d9ab82b596857eea14bf6e04806a6c5a
--
2.17.1
next prev parent reply other threads:[~2023-01-21 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:58 [PATCH v5 " Chang S. Bae
2022-09-22 19:58 ` [PATCH v5 1/4] Documentation/x86: Explain the purpose for dynamic features Chang S. Bae
2022-09-22 19:58 ` [PATCH v5 2/4] x86/arch_prctl: Add AMX feature numbers as ABI constants Chang S. Bae
2022-09-22 19:58 ` [PATCH v5 3/4] Documentation/x86: Add the AMX enabling example Chang S. Bae
2022-09-22 19:58 ` [PATCH v5 4/4] Documentation/x86: Explain the state component permission for guests Chang S. Bae
2023-01-21 0:18 ` Chang S. Bae [this message]
2023-01-21 0:18 ` [PATCH v5 RESEND 1/4] Documentation/x86: Explain the purpose for dynamic features Chang S. Bae
2023-01-21 0:18 ` [PATCH v5 RESEND 2/4] x86/arch_prctl: Add AMX feature numbers as ABI constants Chang S. Bae
2023-01-21 0:18 ` [PATCH v5 RESEND 3/4] Documentation/x86: Add the AMX enabling example Chang S. Bae
2023-01-21 0:19 ` [PATCH v5 RESEND 4/4] Documentation/x86: Explain the state component permission for guests 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=20230121001900.14900-1-chang.seok.bae@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yang.zhong@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®