From: Hajime Tazaki <thehajime@gmail.com>
To: linux-um@lists.infradead.org
Cc: ricarkol@google.com, Liam.Howlett@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 00/14] nommu UML
Date: Thu, 18 Sep 2025 16:38:12 +0900 [thread overview]
Message-ID: <m2bjn88b2z.wl-thehajime@gmail.com> (raw)
In-Reply-To: <cover.1758171893.git.thehajime@gmail.com>
sorry,
I included an unintentional patch in the series ([PATCH v11 06/14])
so, will resend this version very soon.
-- Hajime
On Thu, 18 Sep 2025 14:15:53 +0900,
Hajime Tazaki wrote:
>
> This patchset is another spin of nommu mode addition to UML. It would
> be nice to hear about your opinions on that.
>
> There are still several limitations/issues which we already found;
> here is the list of those issues.
>
> - memory mapped by loadable modules are not distinguished from
> userspace memory.
>
> -- Hajime
>
> v11:
> - clean up userspace return routine and integrate to userspace() ([04/13])
> - fix direction flag issue on using nolibc memcpy ([04/13])
> - fix a crash issue when using usermode helper ([06/13])
> - test with out-of-tree kunit-uapi patches (which uses umh)
> - https://lore.kernel.org/all/20250626-kunit-kselftests-v4-0-48760534fef5@linutronix.de/
> - https://lore.kernel.org/all/20250626195714.2123694-3-benjamin@sipsolutions.net/
prev parent reply other threads:[~2025-09-18 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 5:15 [PATCH v11 00/14] nommu UML Hajime Tazaki
2025-09-18 5:15 ` [PATCH v11 01/14] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-09-18 5:15 ` [PATCH v11 02/14] um: decouple MMU specific code from the common part Hajime Tazaki
2025-09-18 5:15 ` [PATCH v11 03/14] um: nommu: memory handling Hajime Tazaki
2025-09-18 5:15 ` [PATCH v11 04/14] x86/um: nommu: syscall handling Hajime Tazaki
2025-09-18 5:15 ` [PATCH v11 05/14] um: nommu: seccomp syscalls hook Hajime Tazaki
2025-09-18 5:15 ` [PATCH v11 06/14] fixup seccomp Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 07/14] x86/um: nommu: process/thread handling Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 08/14] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 09/14] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 10/14] x86/um: nommu: signal handling Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 11/14] um: nommu: a work around for MMU dependency to PCI driver Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 12/14] um: change machine name for uname output Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 13/14] um: nommu: add documentation of nommu UML Hajime Tazaki
2025-09-18 5:16 ` [PATCH v11 14/14] um: nommu: plug nommu code into build system Hajime Tazaki
2025-09-18 7:38 ` Hajime Tazaki [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=m2bjn88b2z.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=ricarkol@google.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.