From: Hajime Tazaki <thehajime@gmail.com>
To: linux-um@lists.infradead.org
Cc: thehajime@gmail.com, ricarkol@google.com,
Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org
Subject: [PATCH v11 11/14] um: nommu: a work around for MMU dependency to PCI driver
Date: Thu, 18 Sep 2025 14:16:04 +0900 [thread overview]
Message-ID: <3cdc0df9917b2acdd718dc2587ae1bddb9258b06.1758171893.git.thehajime@gmail.com> (raw)
In-Reply-To: <cover.1758171893.git.thehajime@gmail.com>
The commit 8fe743b5eba0 ("PCI: Add CONFIG_MMU dependency") restricts the
PCI base driver to depend on MMU. While nommu UML _can_ implement PCI
drivers over PCI devices (e.g., virtio-pci), the current nommu UML
doesn't implement it.
But without PCI drivers kunit complains as config for kunit
(arch_uml.config) defines the dependency to PCI drivers.
This commit fixes the issue of this compile failures when building PCI
drivers with nommu UML. In particular, the fix is to undefine the
constant PCI_IOBASE to be able to bypass pci_unmap_iospace() call.
When we will support PCI drivers for nommu UML, we will refactor this
code.
Signed-off-by: Hajime Tazaki <thehajime@gmail.com>
---
arch/um/include/asm/dma.h | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/arch/um/include/asm/dma.h b/arch/um/include/asm/dma.h
index fdc53642c718..643d74555671 100644
--- a/arch/um/include/asm/dma.h
+++ b/arch/um/include/asm/dma.h
@@ -4,6 +4,19 @@
#include <asm/io.h>
+/**
+ * now the PCI core driver depends on CONFIG_MMU in linus tree, nommu
+ * UML cannot build with PCI but without PCI kunit doesn't build due
+ * to the dependency to the CONFIG_VIRTIO_UML.
+ *
+ * This is a workaround to silence build failures on kunit, which is
+ * valid until nommu UML supports PCI drivers (e.g., virtio-pci) in a
+ * future.
+ */
+#ifndef CONFIG_MMU
+#undef PCI_IOBASE
+#endif
+
extern unsigned long uml_physmem;
#define MAX_DMA_ADDRESS (uml_physmem)
--
2.43.0
next prev parent reply other threads:[~2025-09-18 5:16 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 ` Hajime Tazaki [this message]
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 ` [PATCH v11 00/14] nommu UML Hajime Tazaki
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=3cdc0df9917b2acdd718dc2587ae1bddb9258b06.1758171893.git.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®