linux-um archives
 help / color / mirror / Atom feed
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 12:50:45 +0100	[thread overview]
Message-ID: <amH-fdSinCFd6sQ_@lucifer> (raw)
In-Reply-To: <20260723093633.140989-12-johannes@sipsolutions.net>

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!

I may pull this series locally and have a play... :)

>
> I cleaned up and added the docs commit now, other changes:
>  - fixed futex implementation after discussions
>  - fixed regression in earlier uname change
>
> johannes
>

Cheers, Lorenzo

[0]:https://lore.kernel.org/all/m2framxerm.wl-thehajime@gmail.com/


  parent reply	other threads:[~2026-07-23 11:51 UTC|newest]

Thread overview: 23+ 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-24  6:50   ` Hajime Tazaki
2026-07-24  6:54     ` Johannes Berg
2026-07-24  7:16       ` Hajime Tazaki
2026-07-24  7:18         ` Hajime Tazaki
2026-07-24  7:18         ` 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-24  6:20   ` Hajime Tazaki
2026-07-24  6:49     ` Johannes Berg
2026-07-24  6:53       ` Hajime Tazaki
2026-07-23 11:50 ` Lorenzo Stoakes (ARM) [this message]
2026-07-23 12:22   ` [PATCH v2 00/10] simplified UML/NOMMU approach Johannes Berg
2026-07-23 15:11     ` Lorenzo Stoakes (ARM)

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=amH-fdSinCFd6sQ_@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox