From: Yeoreum Yun <yeoreum.yun@arm.com>
To: catalin.marinas@arm.com, pcc@google.com, will@kernel.org,
broonie@kernel.org, anshuman.khandual@arm.com,
joey.gouly@arm.com, yury.khrustalev@arm.com, maz@kernel.org,
oliver.upton@linux.dev, frederic@kernel.org,
shmeerali.kolothum.thodi@huawei.com, james.morse@arm.com,
mark.rutland@arm.com, huangxiaojia2@huawei.com,
akpm@linux-foundation.org, surenb@google.com,
robin.murphy@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Yeoreum Yun <yeoreum.yun@arm.com>
Subject: [PATCH v4 0/6] support FEAT_MTE_TAGGED_FAR feature
Date: Wed, 7 May 2025 10:57:51 +0100 [thread overview]
Message-ID: <20250507095757.1663684-1-yeoreum.yun@arm.com> (raw)
The FEAT_MTE_TAGGED_FAR feature provides support for
reporting all non-address bits during a synchronous MTE tag check fault.
This patchset extends the reporting tag to include
not only the memory tag (logical tag) but also the address tag via
si_addr when FEAT_MTE_TAGGED_FAR feature is supported.
Patch Sequences
================
Patch #1 adds cpufeature FEAT_MTE_TAGGED_FAR
Patch #2 adds MTE_FAR hwcaps and export address tag when it supports
Patch #3 adds mtefar hwcap test
Patch #4 prepares to add mtefar testcase
Patch #5 refactor check_mmap_option with loop to add mtefar testcase
Patch #6 adds mtefar test cases corresponding to
each testcase of check_mmap_options
Patch History
================
v3 to v4:
- fix hwcap string for FEAT_MTE_TAGGED_FAR
- split cpufeature and hwcap modification and merge hwcap's
modification with exporting address tag patch
- add mtefar testcase on check_mmap_options
- https://lore.kernel.org/all/20250410074721.947380-1-yeoreum.yun@arm.com/
v2 to v3:
- Rebase to 6.15-rc1
- https://lore.kernel.org/all/20250403172758.67106-1-yeoreum.yun@arm.com/
v1 to v2:
- add hwcap test for MTE_FAR feature.
- add MTE_FAR doc into elf_hwcap.rst
- https://lore.kernel.org/all/20250403142707.26397-1-yeoreum.yun@arm.com/
Yeoreum Yun (6):
arm64/cpufeature: add FEAT_MTE_TAGGED_FAR feature
arm64: report address tag when FEAT_MTE_TAGGED_FAR is supported
tools/kselftest: add MTE_FAR hwcap test
kselftest/arm64/mte: preparation for mtefar test
kselftest/arm64/mte: refactor check_mmap_option test
kselftest/arm64/mte: add mtefar test on check_mmap_option
Documentation/arch/arm64/elf_hwcaps.rst | 3 +
Documentation/arch/arm64/tagged-pointers.rst | 11 +-
arch/arm64/include/asm/hwcap.h | 1 +
arch/arm64/include/uapi/asm/hwcap.h | 1 +
arch/arm64/kernel/cpufeature.c | 9 +
arch/arm64/kernel/cpuinfo.c | 1 +
arch/arm64/mm/fault.c | 7 +-
arch/arm64/tools/cpucaps | 1 +
tools/testing/selftests/arm64/abi/hwcap.c | 6 +
.../selftests/arm64/mte/check_buffer_fill.c | 2 +-
.../selftests/arm64/mte/check_child_memory.c | 4 +-
.../arm64/mte/check_hugetlb_options.c | 4 +-
.../selftests/arm64/mte/check_ksm_options.c | 4 +-
.../selftests/arm64/mte/check_mmap_options.c | 244 +++++++++++++-----
.../arm64/mte/check_tags_inclusion.c | 2 +-
.../selftests/arm64/mte/check_user_mem.c | 2 +-
.../selftests/arm64/mte/mte_common_util.c | 70 ++++-
.../selftests/arm64/mte/mte_common_util.h | 8 +-
tools/testing/selftests/arm64/mte/mte_def.h | 8 +
19 files changed, 291 insertions(+), 97 deletions(-)
--
LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
next reply other threads:[~2025-05-07 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 9:57 Yeoreum Yun [this message]
2025-05-07 9:57 ` [PATCH v4 1/6] arm64/cpufeature: add " Yeoreum Yun
2025-05-07 9:57 ` [PATCH v4 2/6] arm64: report address tag when FEAT_MTE_TAGGED_FAR is supported Yeoreum Yun
2025-05-07 9:57 ` [PATCH v4 3/6] tools/kselftest: add MTE_FAR hwcap test Yeoreum Yun
2025-05-07 9:57 ` [PATCH v4 4/6] kselftest/arm64/mte: preparation for mtefar test Yeoreum Yun
2025-05-07 9:57 ` [PATCH v4 5/6] kselftest/arm64/mte: refactor check_mmap_option test Yeoreum Yun
2025-05-07 9:57 ` [PATCH v4 6/6] kselftest/arm64/mte: add mtefar test on check_mmap_option Yeoreum Yun
2025-05-19 8:13 ` [PATCH v4 0/6] support FEAT_MTE_TAGGED_FAR feature Yeoreum Yun
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=20250507095757.1663684-1-yeoreum.yun@arm.com \
--to=yeoreum.yun@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=frederic@kernel.org \
--cc=huangxiaojia2@huawei.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pcc@google.com \
--cc=robin.murphy@arm.com \
--cc=shmeerali.kolothum.thodi@huawei.com \
--cc=surenb@google.com \
--cc=will@kernel.org \
--cc=yury.khrustalev@arm.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®