From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com
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 v4 0/4] Documentation/x86: Improve the AMX documentation
Date: Fri, 9 Sep 2022 13:15:36 -0700 [thread overview]
Message-ID: <20220909201540.17705-1-chang.seok.bae@intel.com> (raw)
Hi all,
Here are the changes from the last version [1]:
* Add the motivation for the dynamic feature enabling.
* Add the description for the guest options back.
Thank you Tony for the review.
=== Cover Letter ===
When the AMX feature was supported in Linux, the dynamic feature enabling
model was introduced. The following documentation changes were considered
to help users to adopt this new enabling model:
(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 motiviation will provide the context of this.
(4) Lastly, the description of new guest options are added as missing.
If they are acceptable, the arch_prctl(2) manual page [2] will be followed
up separately with something similar to the kernel documentation.
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/20220711171347.27309-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 | 98 +++++++++++++++++++++++++++++++
arch/x86/include/uapi/asm/prctl.h | 3 +
2 files changed, 101 insertions(+)
base-commit: 132bde89b5234d0ca8909775b354c48b214e1abc
--
2.17.1
next reply other threads:[~2022-09-09 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 20:15 Chang S. Bae [this message]
2022-09-09 20:15 ` [PATCH v4 1/4] Documentation/x86: Explain the purpose for dynamic features Chang S. Bae
2022-09-09 21:36 ` Dave Hansen
2022-09-14 5:25 ` Chang S. Bae
2022-09-09 20:15 ` [PATCH v4 2/4] x86/arch_prctl: Add AMX feature numbers as ABI constants Chang S. Bae
2022-09-09 20:15 ` [PATCH v4 3/4] Documentation/x86: Add the AMX enabling example Chang S. Bae
2022-09-09 20:15 ` [PATCH v4 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=20220909201540.17705-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;
as well as URLs for NNTP newsgroup(s).