Thomas Weißschuh 031cdd3bc3 kunit: Enable PCI on UML without triggering WARN() ... Various KUnit tests require PCI infrastructure to work. All normal platforms enable PCI by default, but UML does not. Enabling PCI from .kunitconfig files is problematic as it would not be portable. So in commit 6fc3a8636a ("kunit: tool: Enable virtio/PCI by default on UML") PCI was enabled by way of CONFIG_UML_PCI_OVER_VIRTIO=y. However CONFIG_UML_PCI_OVER_VIRTIO requires additional configuration of CONFIG_UML_PCI_OVER_VIRTIO_DEVICE_ID or will otherwise trigger a WARN() in virtio_pcidev_init(). However there is no one correct value for UML_PCI_OVER_VIRTIO_DEVICE_ID which could be used by default. This warning is confusing when debugging test failures. On the other hand, the functionality of CONFIG_UML_PCI_OVER_VIRTIO is not used at all, given that it is completely non-functional as indicated by the WARN() in question. Instead it is only used as a way to enable CONFIG_UML_PCI which itself is not directly configurable. Instead of going through CONFIG_UML_PCI_OVER_VIRTIO, introduce a custom configuration option which enables CONFIG_UML_PCI without triggering warnings or building dead code. Link: https://lore.kernel.org/r/20250908-kunit-uml-pci-v2-1-d8eba5f73c9d@linutronix.de Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Reviewed-by: Johannes Berg <johannes@sipsolutions.net> Reviewed-by: David Gow <davidgow@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>		2025-09-15 10:29:59 -06:00
..
all_tests.config	Revert "kunit: configs: Enable CONFIG_INIT_STACK_ALL_PATTERN in all_tests"	2025-06-03 11:20:21 +02:00
arch_uml.config	kunit: Enable PCI on UML without triggering WARN()	2025-09-15 10:29:59 -06:00
coverage_uml.config	kunit: add coverage_uml.config to enable GCOV on UML	2022-07-07 18:06:36 -06:00
default.config	kunit: Move default config from arch/um -> tools/testing/kunit	2021-06-23 17:49:17 -06:00