From: Eric Auger <eric.auger@xxxxxxxxxx> redhat/configs: Fix CONFIG_VIRTIO_IOMMU to 'y' on aarch64 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1972795 Upstream Status: RHEL only Tested: on ARM with qemu (Jean-Philippe Brucker's qemu branch as the qemu integration is not yet upstream, with both protected virtio-blk-pci and a virtio-net-pci devices) Commit fe6d9534dbe4 ("redhat/configs: Set CONFIG_VIRTIO_IOMMU on aarch64") enabled the compilation of the virtio-iommu driver on ARM but set the config to 'm'. However if there are devices behind the vIOMMU that are needed during the boot such as a virtio-blk-pci device, the guest fails to boot as the driver is not loaded. Let's fix this bootstrap issue by compiling the driver in-kernel as it is done for other iommu drivers. Signed-off-by: Eric Auger <eric.auger@xxxxxxxxxx> diff --git a/redhat/configs/common/generic/arm/aarch64/CONFIG_VIRTIO_IOMMU b/redhat/configs/common/generic/arm/aarch64/CONFIG_VIRTIO_IOMMU index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/arm/aarch64/CONFIG_VIRTIO_IOMMU +++ b/redhat/configs/common/generic/arm/aarch64/CONFIG_VIRTIO_IOMMU @@ -1 +1 @@ -CONFIG_VIRTIO_IOMMU=m +CONFIG_VIRTIO_IOMMU=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1289 _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
