linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Tang <danielzgtg.opensource@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-doc@vger.kernel.org, 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>
Subject: [PATCH v2] Documentation/protection-keys: Mark as available on AMD
Date: Wed, 19 Nov 2025 19:47:20 -0500	[thread overview]
Message-ID: <2728119.mhk5qWAgFL@daniel-desktop3> (raw)
In-Reply-To: <20251119215038.GHaR47rlpLKZlu-m0y@fat_crate.local>

This is shown on page 78 of AMD document 55898 "Preliminary Processor
Programming Reference (PPR) for AMD Family 19h Model 01h, Revision B1
Processors Volume 1 of 2" for Zen 3.

I tested this on my 5900X via the program in pkeys(7) and
`grep ospke /proc/cpuinfo`.

Signed-off-by: Daniel Tang <danielzgtg.opensource@gmail.com>
---
 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





  reply	other threads:[~2025-11-20  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 14:01 [PATCH] Documentation/protection-keys: Mark as available on AMD Daniel Tang
2025-11-19 21:50 ` Borislav Petkov
2025-11-20  0:47   ` Daniel Tang [this message]
2025-11-20  1:08   ` 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=2728119.mhk5qWAgFL@daniel-desktop3 \
    --to=danielzgtg.opensource@gmail.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.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).