From: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
To: peterz@infradead.org, will@kernel.org, oleg@redhat.com,
xin@zytor.com, maciej.wieczor-retman@intel.com,
dave.hansen@linux.intel.com, tglx@kernel.org,
james.morse@arm.com, akpm@linux-foundation.org,
seanjc@google.com, ryan.roberts@arm.com, riel@surriel.com,
mingo@redhat.com, shuah@kernel.org, hpa@zytor.com,
brgerst@gmail.com, bp@alien8.de, luto@kernel.org,
baohua@kernel.org, ubizjak@gmail.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, m.wieczorretman@pm.me
Subject: [PATCH v1 0/4] x86: Simplifying LAM
Date: Fri, 20 Feb 2026 12:46:13 +0000 [thread overview]
Message-ID: <cover.1771589807.git.m.wieczorretman@pm.me> (raw)
After ChkTag [1] announcement, it's worth preparing a stable x86 linear
address masking (lam) user interface. One important aspect of lam is the
tag width, and aligning it with other industry solutions can provide a
more popular, generalized interface that other technologies could
utilize.
ChkTag will use 4-bit tags and since that's the direction other memory
tagging implementations seem to be taking too (for example Arm's MTE)
it's reasonable to converge lam in linux to the same specification. Even
though x86's LAM supports 6-bit tags it is beneficial to default lam to
4 bits as ChkTag will likely be the main user of the interface and such
connection should simplify things in the future.
6-bit tags should still be available as a debug feature and possible to
enable through debugfs. Tag width can be system wide whether it's the
default 4 bits or debug 6 bits and when a process requests a specific tag
width it should get the max amount enabled globally.
Series also cleans up some comments referencing LAM_U48 which was not
implemented in the kernel and the comments shouldn't imply it can be
enabled.
Patches are based on v6.19.
[1] https://community.intel.com/t5/Blogs/Tech-Innovation/open-intel/ChkTag-x86-Memory-Safety/post/1721490
Maciej Wieczor-Retman (4):
x86/process: Shorten the default LAM tag width
x86/process: Add a debug interface to change LAM tag width
x86/mm: Cleanup comments where LAM_U48 is mentioned
selftests/lam: Add test cases for different LAM tag widths
arch/x86/include/asm/mmu.h | 2 +-
arch/x86/include/asm/mmu_context.h | 3 ++
arch/x86/include/asm/tlbflush.h | 2 +-
arch/x86/kernel/process_64.c | 71 +++++++++++++++++++++---
tools/testing/selftests/x86/lam.c | 87 +++++++++++++++++++++++++-----
5 files changed, 144 insertions(+), 21 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-20 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 12:46 Maciej Wieczor-Retman [this message]
2026-02-20 12:48 ` [PATCH v1 1/4] x86/process: Shorten the default LAM tag width Maciej Wieczor-Retman
2026-02-20 12:48 ` [PATCH v1 2/4] x86/process: Add a debug interface to change " Maciej Wieczor-Retman
2026-02-20 16:41 ` kernel test robot
2026-02-20 16:57 ` Maciej Wieczor-Retman
2026-02-20 12:48 ` [PATCH v1 3/4] x86/mm: Cleanup comments where LAM_U48 is mentioned Maciej Wieczor-Retman
2026-02-20 12:49 ` [PATCH v1 4/4] selftests/lam: Add test cases for different LAM tag widths Maciej Wieczor-Retman
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=cover.1771589807.git.m.wieczorretman@pm.me \
--to=m.wieczorretman@pm.me \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@kernel.org \
--cc=ubizjak@gmail.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.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®