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 v5 1/2] selftests: run tests on nommu architecture
Date: Mon, 12 Oct 2026 12:53:08 +0200 [thread overview]
Message-ID: <b971a37e-9425-4acc-b868-682cc9480273@kernel.org> (raw)
In-Reply-To: <20261006085642.3852152-2-thehajime@gmail.com>
On 10/6/26 10:56, Hajime Tazaki wrote:
> Architectures lacking MMU don't support fork(2) syscall and only
> vfork(2) is available with limitations. Thus, we cannot run kselftest
> on nommu architecture as is.
>
> This commit addresses this issue with the following changes:
>
> - Detect NOMMU at runtime from the MmapCopy field in /proc/meminfo
> and avoid timeout, which requires fork(2).
> - Document how to build and run the NOMMU tests, including the procfs
> prerequisite for runtime detection.
>
> Build and run the tests with:
>
> $ make ARCH=um O=build kselftest-all TARGETS=nommu
> $ make ARCH=um O=build kselftest-install TARGETS=nommu
> $ ./build/kselftest/kselftest_install/run_kselftest.sh -p -c nommu
>
> Cc: Shuah Khan <shuah@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Kees Cook <kees@kernel.org>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: Will Drewry <wad@chromium.org>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Brendan Jackman <brendan.jackman@linux.dev>
> Cc: Hangbin Liu <liuhangbin@gmail.com>
> Cc: "Ricardo B. Marliere" <rbm@suse.com>
> Cc: linux-kselftest@vger.kernel.org
> Cc: linux-um@lists.infradead.org
> Cc: linux-mm@kvack.org
> Cc: linux-doc@vger.kernel.org
> Closes: https://sashiko.dev/#/patchset/20260813063401.1786548-1-thehajime%40gmail.com
> Signed-off-by: Hajime Tazaki <thehajime@gmail.com>
>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-10-12 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:56 [PATCH v5 0/2] support kselftest on nommu platform Hajime Tazaki
2026-10-06 8:56 ` [PATCH v5 1/2] selftests: run tests on nommu architecture Hajime Tazaki
2026-10-12 10:53 ` David Hildenbrand (Arm) [this message]
2026-10-06 8:56 ` [PATCH v5 2/2] selftests/nommu: add nommu mmap and mremap behavior tests Hajime Tazaki
2026-10-07 19:30 ` [PATCH v5 0/2] support kselftest on nommu platform Andrew Morton
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=b971a37e-9425-4acc-b868-682cc9480273@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox