From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-um@lists.infradead.org, Hajime Tazaki <thehajime@gmail.com>,
liam@infradead.org, Ricardo Koller <ricarkol@google.com>
Subject: Re: [PATCH v2 00/10] simplified UML/NOMMU approach
Date: Thu, 23 Jul 2026 16:11:15 +0100 [thread overview]
Message-ID: <amIuutfG32p10iTV@lucifer> (raw)
In-Reply-To: <07b3c945a5aeeb08fb25955fb072308e3744402e.camel@sipsolutions.net>
On Thu, Jul 23, 2026 at 02:22:50PM +0200, Johannes Berg wrote:
> On Thu, 2026-07-23 at 12:50 +0100, Lorenzo Stoakes (ARM) wrote:
> > On Thu, Jul 23, 2026 at 11:35:41AM +0200, Johannes Berg wrote:
> > > Prior RFC/v1 was here:
> > > https://lore.kernel.org/linux-um/20260720185103.530603-11-johannes@sipsolutions.net/
> >
> > Thanks for this! I really really want a nommu UML mode for testing purposes so
> > I'm very happy you're doing this :)
>
> :)
>
> > One mildly annoying note though - it'd be good for the cover letter to summarise
> > what the series is about, what it achieves, how it compares for instance to
> > Hajime's original approach ([0]).
> >
> > I guess how cover letters are used varies by subsystem somewhat but I find it
> > really actively useful to see a summary in the cover letter.
> >
> > Anyway reading thorugh the RFC which already covers this seems that this
> > achieves nommu UML with less changes needed which sounds really interesting!
>
> Right, sorry, I got lazy and didn't copy/paste the RFC cover letter but
> only put the link to it instead. Is there something beyond what I wrote
> there that you were looking for?
No, I think the previous version covered it off well, just a nag (hence being
self aware about the mildly annoying nature of it :P)
UML isn't really my area so can't give in-depth review but I really want
this to be a thing so happy to be cc'd on this!
>
>
> > I may pull this series locally and have a play... :)
>
> If you do, let us know how it goes :)
Will do! :)
>
> johannes
Cheers, Lorenzo
prev parent reply other threads:[~2026-07-23 15:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 9:35 [PATCH v2 00/10] simplified UML/NOMMU approach Johannes Berg
2026-07-23 9:35 ` [PATCH v2 01/10] x86/um: nommu: elf loader for fdpic Johannes Berg
2026-07-23 9:35 ` [PATCH v2 02/10] um: decouple MMU specific code from the common part Johannes Berg
2026-07-23 9:35 ` [PATCH v2 03/10] um: nommu: memory handling Johannes Berg
2026-07-23 9:35 ` [PATCH v2 04/10] um: change machine name for uname output Johannes Berg
2026-07-23 9:35 ` [PATCH v2 05/10] x86/um/vdso: nommu: vdso memory update Johannes Berg
2026-07-23 9:35 ` [PATCH v2 06/10] um: further decouple MMU related code Johannes Berg
2026-07-23 9:35 ` [PATCH v2 07/10] um: nommu: add SMP futex operations Johannes Berg
2026-07-23 9:35 ` [PATCH v2 08/10] um: nommu: add userspace runner processes Johannes Berg
2026-07-23 13:59 ` Johannes Berg
2026-07-23 9:35 ` [PATCH v2 09/10] um: allow deselecting CONFIG_MMU Johannes Berg
2026-07-23 9:35 ` [PATCH v2 10/10] Documentation: um: document nommu UML Johannes Berg
2026-07-23 11:50 ` [PATCH v2 00/10] simplified UML/NOMMU approach Lorenzo Stoakes (ARM)
2026-07-23 12:22 ` Johannes Berg
2026-07-23 15:11 ` Lorenzo Stoakes (ARM) [this message]
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=amIuutfG32p10iTV@lucifer \
--to=ljs@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=liam@infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=ricarkol@google.com \
--cc=thehajime@gmail.com \
/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.