From: Hajime Tazaki <thehajime@gmail.com>
To: johannes@sipsolutions.net
Cc: geert@linux-m68k.org, linux-um@lists.infradead.org,
ricarkol@google.com, Liam.Howlett@oracle.com,
linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH RESEND v11 10/13] um: nommu: a work around for MMU dependency to PCI driver
Date: Wed, 24 Sep 2025 08:51:50 +0900 [thread overview]
Message-ID: <m2zfak7mnd.wl-thehajime@gmail.com> (raw)
In-Reply-To: <23adb61e95275251e459513a03ab7d2bcf1f2e07.camel@sipsolutions.net>
Hello Geert, Johannes,
On Wed, 24 Sep 2025 02:13:47 +0900,
Johannes Berg wrote:
>
> On Tue, 2025-09-23 at 17:42 +0200, Geert Uytterhoeven wrote:
> > >
> > > currently, drivers/pci/Kconfig (CONFIG_PCI) marks as depends on MMU,
> > > so we cannot select it when CONFIG_MMU=n.
> >
> > That is a fairly recent change, see commit 8fe743b5eba0abfb ("PCI:
> > Add CONFIG_MMU dependency") in v6.16-rc1. As this is not a "hard"
> > dependency, perhaps it should be reverted, iff you are willing to take
> > care of the casual breakage?
>
> Why though? UML with PCI can't really be a functional thing, only a
> testing thing, and testing PCI on !MMU when that is actually impossible
> in non-simulation is pointless?
currently nommu UML doesn't come with using PCI except building under
kunit (ARCH=um), but I have in my mind to use it under !MMU
environment, so would be an option in the future.
and this series doesn't include PCI w/ !MMU.
so, I would propose the modification to revert the MMU dependency when
time has come.
btw, what do you mean by "hard" dependency in this context, Geert ?
-- Hajime
next prev parent reply other threads:[~2025-09-23 23:51 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
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 [this message]
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=m2zfak7mnd.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--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.