From: Johannes Berg <johannes@sipsolutions.net>
To: Hajime Tazaki <thehajime@gmail.com>
Cc: linux-um@lists.infradead.org, ricarkol@google.com,
Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v11 10/13] um: nommu: a work around for MMU dependency to PCI driver
Date: Fri, 19 Sep 2025 09:24:07 +0200 [thread overview]
Message-ID: <6b1abe384237c8129e8043ecdfdad77758d2fd2f.camel@sipsolutions.net> (raw)
In-Reply-To: <m28qib8g1r.wl-thehajime@gmail.com> (sfid-20250919_020320_735898_47C8CCD7)
On Fri, 2025-09-19 at 09:03 +0900, Hajime Tazaki wrote:
> > This doesn't make a lot of sense to me. Why would we even want to build
> > PCI on NOMMU-UML if PCI in general is dependent on MMU now?
> >
> > It's not like ARCH=um with PCI and NOMMU has any value even for testing
> > if such a configuration cannot exist in reality?
>
> totally understand your point.
>
> now I see that we don't have to have this work around by using
> --kconfig_add option to kunit.py.
>
> # like --kconfig_add CONFIG_UML_PCI_OVER_VIRTIO=n (in addition to
> --kconfig_add CONFIG_MMU=n).
That's not what I mean. I think it should be made impossible to build
the broken code.
The problem is probably UML_PCI_OVER_VIRTIO selecting UML_PCI selecting
various PCI code, but nothing depends on PCI in the first place. Which
it should, then?
johannes
next prev parent reply other threads:[~2025-09-19 7:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 7:38 [PATCH RESEND v11 00/13] nommu UML Hajime Tazaki
2025-09-18 7:38 ` [PATCH RESEND v11 01/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-09-18 7:38 ` [PATCH RESEND v11 02/13] um: decouple MMU specific code from the common part Hajime Tazaki
2025-09-18 7:38 ` [PATCH RESEND v11 03/13] um: nommu: memory handling Hajime Tazaki
2025-09-18 7:38 ` [PATCH RESEND v11 04/13] x86/um: nommu: syscall handling Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 05/13] um: nommu: seccomp syscalls hook Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 06/13] x86/um: nommu: process/thread handling Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 07/13] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 08/13] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 09/13] x86/um: nommu: signal handling Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 10/13] um: nommu: a work around for MMU dependency to PCI driver Hajime Tazaki
2025-09-18 8:30 ` Johannes Berg
2025-09-19 0:03 ` Hajime Tazaki
2025-09-19 7:24 ` Johannes Berg [this message]
2025-09-19 9:32 ` Hajime Tazaki
2025-09-19 9:38 ` Johannes Berg
2025-09-19 9:38 ` Johannes Berg
2025-09-19 9:43 ` Johannes Berg
2025-09-19 23:46 ` Hajime Tazaki
2025-09-22 6:32 ` Johannes Berg
2025-09-23 23:44 ` Hajime Tazaki
2025-09-23 15:42 ` Geert Uytterhoeven
2025-09-23 17:13 ` Johannes Berg
2025-09-23 23:51 ` Hajime Tazaki
2025-09-24 8:02 ` Geert Uytterhoeven
2025-09-24 11:03 ` Arnd Bergmann
2025-09-24 23:27 ` Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 11/13] um: change machine name for uname output Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 12/13] um: nommu: add documentation of nommu UML Hajime Tazaki
2025-09-18 7:39 ` [PATCH RESEND v11 13/13] um: nommu: plug nommu code into build system Hajime Tazaki
2025-09-18 10:39 ` [PATCH RESEND v11 00/13] nommu UML 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=6b1abe384237c8129e8043ecdfdad77758d2fd2f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.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.