From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: 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, david@kernel.org,
liuhangbin@gmail.com, corbet@lwn.net, kees@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,
geert@linux-m68k.org, daniel@thingy.jp
Subject: Re: [PATCH v3 2/3] selftests: run tests on nommu architecture
Date: Mon, 28 Sep 2026 12:00:19 +0100 [thread overview]
Message-ID: <arpIi5QBG1_MuZzJ@gremlin> (raw)
In-Reply-To: <04259a99ed91f8a527b255951a6f626310728170.camel@sipsolutions.net>
On Mon, Sep 28, 2026 at 09:44:49AM +0200, Johannes Berg wrote:
> On Sat, 2026-09-26 at 10:08 +0900, Hajime Tazaki wrote:
> > Architectures lacks MMU doesn't support fork(2) syscall and only
>
> nit: Architectures lacking MMU don't support the fork(2) syscall ...
>
> Not sure where this should be merged? I guess selftests would make most
> sense, but you can't actually test it out before the UML nommu changes,
> so that doesn't work too well right now?
I seem to recall Hajime saying he tested this on an actual nommu
device/virtualised equivalent so nommu UML isn't strictly necessary (though very
nice to have!)
I think I saw something fly by that implied it might be coming in 7.4 is that
so? :)
>
> johannes
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-09-28 11:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 1:08 [PATCH v3 0/3] support kselftest on nommu platform Hajime Tazaki
2026-09-26 1:08 ` [PATCH v3 1/3] selftests: kselftest: avoid cd - in runner Hajime Tazaki
2026-09-28 9:25 ` David Hildenbrand (Arm)
2026-09-28 11:02 ` Lorenzo Stoakes (ARM)
2026-09-28 17:27 ` Pedro Falcato
2026-09-28 18:16 ` Pedro Falcato
2026-09-29 1:05 ` Hajime Tazaki
2026-09-26 1:08 ` [PATCH v3 2/3] selftests: run tests on nommu architecture Hajime Tazaki
2026-09-28 7:44 ` Johannes Berg
2026-09-28 11:00 ` Lorenzo Stoakes (ARM) [this message]
2026-09-28 12:32 ` Johannes Berg
2026-09-28 16:23 ` Lorenzo Stoakes (ARM)
2026-09-29 1:03 ` Hajime Tazaki
2026-09-28 11:03 ` Lorenzo Stoakes (ARM)
2026-09-26 1:08 ` [PATCH v3 3/3] selftests/nommu: add nommu mmap and mremap behavior tests Hajime Tazaki
2026-09-28 12:34 ` Mark Brown
2026-09-29 1:06 ` Hajime Tazaki
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=arpIi5QBG1_MuZzJ@gremlin \
--to=ljs@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=david@kernel.org \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--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=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.