All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hajime Tazaki <thehajime@gmail.com>
To: lorenzo.stoakes@oracle.com
Cc: linux-um@lists.infradead.org, ricarkol@google.com,
	Liam.Howlett@oracle.com, richard@nod.at,
	anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 00/13] nommu UML
Date: Sun, 27 Apr 2025 12:49:36 +0900	[thread overview]
Message-ID: <m21pte6z73.wl-thehajime@gmail.com> (raw)
In-Reply-To: <f4242067-0113-432e-b8d1-d26ff5e4a355@lucifer.local>


Hello Lorenzo,

On Fri, 25 Apr 2025 22:49:31 +0900,
Lorenzo Stoakes wrote:

> It seemed this series died, which is a pity, i'd be very useful to have
> this functionality to aid in easily testing nommu in mm code.
> 
> I know that I pushed back a little (or rather - wondering about the status
> of nommu in general) back in v2, however with it confirmed that nommu is
> required, this series becomes really quite important.
> 
> This would need rebasing of course for a v8, but I wonder if there is any
> appetite for it or why this didn't go anywhere?
> 
> In any case, if you are still interested in this Hajime (thanks so much for
> all your hard work on it!), just saying there are definitely users out
> there.

I've been waiting for opinions from the um maintainers to the v7
patchset, and am ready to send v8 series with rebasing the current
uml/next branch.

I believe the v7 series is still in the patchwork queue so, I hope
it'll be reviewed soon.

# thanks for the information that this feature is useful to test mm
  code.

-- Hajime


  reply	other threads:[~2025-04-27  3:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  6:00 [PATCH v7 00/13] nommu UML Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 01/13] x86/um: clean up elf specific definitions Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 02/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 03/13] um: decouple MMU specific code from the common part Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 04/13] um: nommu: memory handling Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 05/13] x86/um: nommu: syscall handling Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 06/13] um: nommu: seccomp syscalls hook Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 07/13] x86/um: nommu: process/thread handling Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 08/13] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 09/13] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 10/13] x86/um: nommu: signal handling Hajime Tazaki
2025-06-19 11:43   ` Benjamin Berg
2025-06-19 12:55     ` Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 11/13] um: change machine name for uname output Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 12/13] um: nommu: add documentation of nommu UML Hajime Tazaki
2025-01-20  6:00 ` [PATCH v7 13/13] um: nommu: plug nommu code into build system Hajime Tazaki
2025-02-04 12:26 ` [PATCH v7 00/13] nommu UML Hajime Tazaki
2025-04-25 13:49 ` Lorenzo Stoakes
2025-04-27  3:49   ` Hajime Tazaki [this message]
2025-04-29 13:23     ` Lorenzo Stoakes
2025-04-30  9:51       ` Johannes Berg
2025-05-01 10:40         ` Lorenzo Stoakes

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=m21pte6z73.wl-thehajime@gmail.com \
    --to=thehajime@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-um@lists.infradead.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=ricarkol@google.com \
    --cc=richard@nod.at \
    /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.