From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Hajime Tazaki <thehajime@gmail.com>,
liam@infradead.org, ljs@kernel.org, vbabka@kernel.org,
jannh@google.com, pfalcato@suse.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] mm: nommu: point to the write iterator upon split_vma
Date: Sun, 5 Jul 2026 22:23:43 -0700 [thread overview]
Message-ID: <20260705222343.5d5c78cbb54839c5efcaabf5@linux-foundation.org> (raw)
In-Reply-To: <aksn5J8Nr0JIsVpQ@casper.infradead.org>
On Mon, 6 Jul 2026 04:58:28 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> On Sun, Jul 05, 2026 at 03:27:08PM -0700, Andrew Morton wrote:
> > Thanks. Unfortunately we aren't very diligent about the nommu code
> > (are we?). Perhaps appropriately - clearly this code doesn't get used a
> > lot.
>
> Should we delete support for NOMMU? As you say, it doesn't get much
> testing, or presumably usage. I have this quote from #m68k a couple of
> years ago...
Greg is busily developing kernel code.
> : I looked at nommu very briefly when I had my 68000 board on the bench
> : but didn’t get anywhere. Also didn’t try particularly hard. I think
> : you are better off with fuzix or OS9 if you want something unixy.
>
> (i suspect Zephyr would also be good, but it doesn't support m68k, just
> arc, arm, arm64, mips, openrisc, renesas rx, riscv, sparc, x86 and xtensa)
Greg, how mush use is NOMMU Linux seeing nowadays?
Thanks.
next prev parent reply other threads:[~2026-07-06 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 1:25 [PATCH] mm: nommu: point to the write iterator upon split_vma Hajime Tazaki
2026-07-05 22:27 ` Andrew Morton
2026-07-06 3:58 ` Matthew Wilcox
2026-07-06 5:23 ` Andrew Morton [this message]
2026-07-06 8:27 ` Geert Uytterhoeven
2026-07-06 11:51 ` Lorenzo Stoakes
2026-07-06 12:57 ` Hajime Tazaki
2026-07-06 9:17 ` Daniel Palmer
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=20260705222343.5d5c78cbb54839c5efcaabf5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerg@uclinux.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=thehajime@gmail.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.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