From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Hajime Tazaki <thehajime@gmail.com>,
linux-mm@kvack.org, liam@infradead.org, rbm@suse.com,
akpm@linux-foundation.org, luto@amacapital.net,
brendan.jackman@linux.dev, liuhangbin@gmail.com, corbet@lwn.net,
kees@kernel.org, ljs@kernel.org, broonie@kernel.org,
mhocko@suse.com, rppt@kernel.org, shuah@kernel.org,
surenb@google.com, vbabka@kernel.org, wad@chromium.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-um@lists.infradead.org
Cc: geert@linux-m68k.org, daniel@thingy.jp
Subject: Re: [PATCH v2 0/2] support kselftest on nommu platform
Date: Tue, 25 Aug 2026 10:37:41 +0200 [thread overview]
Message-ID: <f2ac9432-4fea-4007-aab0-ad80597b284c@kernel.org> (raw)
In-Reply-To: <20260825015945.141739-1-thehajime@gmail.com>
On 8/25/26 03:59, Hajime Tazaki wrote:
> We add an ability to execute kselftest on nommu platforms.
>
> Currently there are several issues if we wish to run kselftests on nommu
> targets:
>
> - it cannot compile/build test binaries because the current files mainly
> assume to build with glibc,
> - some of the tests are not able to run on nommu targets as there are no
> fork(2) syscall.
>
> The first issue can be avoided if we can build static PIE binaries (if
> targets support it), but in our case (build on ubuntu/glibc and run on
> alpine/musl-libc), it fails to invoke due to lack of the GNU ifunc
> mechanism. Thus, we need to cross-compile with musl toolchain, which
> needs to be solved the first issue.
>
> The second issue is the lack of fork(2) syscall on those platforms.
> Especially the test harness helper (kselftest_harness.h) uses the
> syscall, which cannot be simply with vfork(2). `timeout` command used
> in `runner.sh` never works for nommu platform as it uses fork(2).
>
> nommu component in the mm subsystem has several known issues and having
> test cases should help this situation, thus this patchset is very first
> step toward enriching test environment which has not been well tested
> for a while. The test cases is implemented based on the document
> (Documentation/admin-guide/mm/nommu-mmap.rst).
>
> So, for the first step, nommu targets only support low-level API of
> kselftests (kselftest.h), and implement tests in a new target,
> TARGETS=mm/nommu. Other targets are currently not even able to build
> due to toolchain issues but will be addressed once the initial
> introduction which mainly focuses on nommu test will be settled.
>
> The patch was initially combined with other patches but is decoupled to
> only focus on test framework and testcases.
>
> - rfc:
> https://lore.kernel.org/linux-mm/20260813063401.1786548-1-thehajime@gmail.com/
>
> Hajime Tazaki (2):
> selftests: run tests on nommu architecture
> selftests/mm: add nommu mmap and mremap behavior tests
>
> Documentation/dev-tools/kselftest.rst | 14 +
> tools/testing/selftests/Makefile | 1 +
> tools/testing/selftests/kselftest/runner.sh | 9 +-
> tools/testing/selftests/kselftest_harness.h | 4 +
> tools/testing/selftests/lib.mk | 8 +
> tools/testing/selftests/mm/nommu/Makefile | 7 +
> .../selftests/mm/nommu/nommu_mmap_test.c | 265 +++++++++++++
> .../selftests/mm/nommu/nommu_mremap_test.c | 353 ++++++++++++++++++
That's odd.
tools/testing/selftests/mm
itself should know which tests can be built and ran on nommu. nommu-only tests
can be placed in mm/nommu, but I would expect tools/testing/selftests/mm's
Makefile and run script to compile and run only selftests that are supported on
the given platform.
--
Cheers,
David
next prev parent reply other threads:[~2026-08-25 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 1:59 [PATCH v2 0/2] support kselftest on nommu platform Hajime Tazaki
2026-08-25 1:59 ` [PATCH v2 1/2] selftests: run tests on nommu architecture Hajime Tazaki
2026-08-25 13:36 ` Lorenzo Stoakes (ARM)
2026-08-27 8:36 ` Hajime Tazaki
2026-08-27 12:15 ` Mark Brown
2026-08-25 1:59 ` [PATCH v2 2/2] selftests/mm: add nommu mmap and mremap behavior tests Hajime Tazaki
2026-08-25 8:37 ` David Hildenbrand (Arm) [this message]
2026-08-25 13:12 ` [PATCH v2 0/2] support kselftest on nommu platform Lorenzo Stoakes (ARM)
2026-08-25 14:17 ` David Hildenbrand (Arm)
2026-08-25 14:28 ` Lorenzo Stoakes (ARM)
2026-08-27 8:46 ` Hajime Tazaki
2026-08-27 8:49 ` Lorenzo Stoakes (ARM)
2026-08-27 8:57 ` Hajime Tazaki
2026-08-27 11:32 ` Lorenzo Stoakes (ARM)
2026-09-01 14:28 ` Johannes Berg
2026-09-01 14:44 ` Lorenzo Stoakes (ARM)
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=f2ac9432-4fea-4007-aab0-ad80597b284c@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@thingy.jp \
--cc=geert@linux-m68k.org \
--cc=kees@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=liuhangbin@gmail.com \
--cc=ljs@kernel.org \
--cc=luto@amacapital.net \
--cc=mhocko@suse.com \
--cc=rbm@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=thehajime@gmail.com \
--cc=vbabka@kernel.org \
--cc=wad@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.