From: Catalin Marinas <catalin.marinas@arm.com>
To: Muhammad Usama Anjum <usama.anjum@arm.com>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shuah Khan <shuah@kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Mark Brown <broonie@kernel.org>,
Yeoreum Yun <yeoreum.yun@arm.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH 4/4] selftest/arm64: Add MTE test config fragment
Date: Fri, 21 Aug 2026 09:55:44 +0100 [thread overview]
Message-ID: <aogSkJxWf9QndjuE@arm.com> (raw)
In-Reply-To: <20260820153331.2448875-5-usama.anjum@arm.com>
On Thu, Aug 20, 2026 at 04:33:26PM +0100, Muhammad Usama Anjum wrote:
> The arm64 selftest collection has no Kconfig fragment, so kernels built
> with the selftest requirements are not guaranteed to provide the support
> used by the MTE tests.
>
> Add a fragment covering the userspace MTE and tagged-address ABIs, KSM
> and its sysfs interface, explicit HugeTLB mappings and their proc/sysctl
> interfaces, and tmpfs-backed file mappings.
>
> Do not request NUMA solely for the optional KSM merge_across_nodes.
>
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@arm.com>
> ---
> tools/testing/selftests/arm64/mte/config | 8 ++++++++
> 1 file changed, 8 insertions(+)
> create mode 100644 tools/testing/selftests/arm64/mte/config
>
> diff --git a/tools/testing/selftests/arm64/mte/config b/tools/testing/selftests/arm64/mte/config
> new file mode 100644
> index 0000000000000..8587ce70c294a
> --- /dev/null
> +++ b/tools/testing/selftests/arm64/mte/config
> @@ -0,0 +1,8 @@
> +CONFIG_ARM64_MTE=y
> +CONFIG_ARM64_TAGGED_ADDR_ABI=y
> +CONFIG_HUGETLBFS=y
> +CONFIG_KSM=y
> +CONFIG_PROC_FS=y
> +CONFIG_SYSCTL=y
You may want CONFIG_PROC_SYSCTL.
> +CONFIG_SYSFS=y
> +CONFIG_TMPFS=y
These are all covered by defconfig. Are these fragments still necessary?
Or are they supposed to work on custom configs? If the latter EXPERT may
be set, hence the PROC_SYSCTL above. You probably also need SHMEM.
--
Catalin
next prev parent reply other threads:[~2026-08-21 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 15:33 [PATCH 0/4] selftest/arm64: Fix MTE test setup and TAP reporting Muhammad Usama Anjum
2026-08-20 15:33 ` [PATCH 1/4] selftest/arm64: Print TAP header Muhammad Usama Anjum
2026-08-20 15:43 ` Mark Brown
2026-08-20 15:33 ` [PATCH 2/4] selftest/arm64: Treat KSM merge_across_nodes as optional Muhammad Usama Anjum
2026-08-20 16:09 ` Mark Brown
2026-08-21 10:57 ` Muhammad Usama Anjum
2026-08-20 15:33 ` [PATCH 3/4] selftest/arm64: Fix MTE prctl TAP plan Muhammad Usama Anjum
2026-08-20 16:14 ` Mark Brown
2026-08-20 15:33 ` [PATCH 4/4] selftest/arm64: Add MTE test config fragment Muhammad Usama Anjum
2026-08-20 15:38 ` Mark Brown
2026-08-20 15:42 ` Muhammad Usama Anjum
2026-08-20 16:42 ` Mark Brown
2026-08-21 8:01 ` Muhammad Usama Anjum
2026-08-21 8:55 ` Catalin Marinas [this message]
2026-08-21 10:43 ` Muhammad Usama Anjum
2026-08-21 11:38 ` Mark Brown
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=aogSkJxWf9QndjuE@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=amit.kachhap@arm.com \
--cc=andreyknvl@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.org \
--cc=usama.anjum@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@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