linux-um archives
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	 Hajime Tazaki <thehajime@gmail.com>,
	johannes@sipsolutions.net, 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,
	 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,
	daniel@thingy.jp
Subject: Re: [PATCH v4 1/2] selftests: run tests on nommu architecture
Date: Fri, 2 Oct 2026 12:53:31 +0100	[thread overview]
Message-ID: <ar-bIzYDdlOKUqla@gremlin> (raw)
In-Reply-To: <CAMuHMdUKcUxHZKhTEF1gwWrU1o8O6jt6N3r90V5hynrLFdwY0A@mail.gmail.com>

On Fri, Oct 02, 2026 at 01:38:31PM +0200, Geert Uytterhoeven wrote:

> On Fri, 2 Oct 2026 at 10:10, Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:

> > But fork() -> -EINVAL or -ENOSYS = nommu, then just have the child quit and
> > etc. should do it.
>
> fork() is not strictly an MMU-feature (you can implement fork on nommu
> if all memory accesses are done relative to a base address register),
> while I think mprotect() is an MMU-feature. Unless it can also be used
> to change the protection using the one or two BARs most MCU haves?
> Anything else that is a real MMU-feature? Non-identity mmap()?

Does any nommu arch implement fork() in linux?

--
Cheers, Lorenzo


  reply	other threads:[~2026-10-02 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 23:57 [PATCH v4 0/2] support kselftest on nommu platform Hajime Tazaki
2026-09-29 23:57 ` [PATCH v4 1/2] selftests: run tests on nommu architecture Hajime Tazaki
2026-09-30  9:17   ` Lorenzo Stoakes (ARM)
2026-10-01  7:08   ` David Hildenbrand (Arm)
2026-10-01  8:42     ` Lorenzo Stoakes (ARM)
2026-10-01 10:01       ` Johannes Berg
2026-10-02  2:38         ` Hajime Tazaki
2026-10-02  6:08           ` David Hildenbrand (Arm)
2026-10-02  8:10             ` Lorenzo Stoakes (ARM)
2026-10-02 11:38               ` Geert Uytterhoeven
2026-10-02 11:53                 ` Lorenzo Stoakes (ARM) [this message]
2026-10-02 12:21                   ` David Hildenbrand (Arm)
2026-10-03 22:39                     ` Hajime Tazaki
2026-09-29 23:57 ` [PATCH v4 2/2] selftests/nommu: add nommu mmap and mremap behavior tests 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=ar-bIzYDdlOKUqla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox