From: Daniel Tang <danielzgtg.opensource@gmail.com>
To: linux-doc@vger.kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Ira Weiny <ira.weiny@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Babu Moger <babu.moger@amd.com>, Borislav Petkov <bp@suse.de>
Subject: [PATCH] Documentation/protection-keys: Mark as available on AMD
Date: Wed, 19 Nov 2025 09:01:30 -0500 [thread overview]
Message-ID: <3647894.L58v44csPz@daniel-desktop3> (raw)
According to https://www.phoronix.com/news/AMD-PRM-PCID-PKEY .
Tested on a 5900X via the program in pkeys(7) and
`grep ospke /proc/cpuinfo`.
---
Documentation/core-api/protection-keys.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/protection-keys.rst b/Documentation/core-api/protection-keys.rst
index 7eb7c6023e09..59e7c178af4b 100644
--- a/Documentation/core-api/protection-keys.rst
+++ b/Documentation/core-api/protection-keys.rst
@@ -11,7 +11,7 @@ application changes protection domains.
Pkeys Userspace (PKU) is a feature which can be found on:
* Intel server CPUs, Skylake and later
* Intel client CPUs, Tiger Lake (11th Gen Core) and later
- * Future AMD CPUs
+ * AMD Zen 3 and later
* arm64 CPUs implementing the Permission Overlay Extension (FEAT_S1POE)
x86_64
--
2.51.0
next reply other threads:[~2025-11-19 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 14:01 Daniel Tang [this message]
2025-11-19 21:50 ` [PATCH] Documentation/protection-keys: Mark as available on AMD Borislav Petkov
2025-11-20 0:47 ` [PATCH v2] " Daniel Tang
2025-11-20 1:08 ` [PATCH] " Daniel Tang
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=3647894.L58v44csPz@daniel-desktop3 \
--to=danielzgtg.opensource@gmail.com \
--cc=babu.moger@amd.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).