vfio.c is being pulled in from the submodule, but it is not being
compiled/linked by the build environment, causing a "Unknown symbol in module"
error when loading the resulting module.
Adding vfio.o to the kvm-objs variable in x86/Kbuild fixes this issue
Signed-off-by: Jonas Pfoh <p...@sec.in.tum.de>
---
diff --git a/x86/Kbuild b/x86/Kbuild
index d75b756..637b3b1 100644
--- a/x86/Kbuild
+++ b/x86/Kbuild
@@ -1,7 +1,7 @@
obj-m := kvm.o kvm-intel.o kvm-amd.o
kvm-objs := kvm_main.o x86.o mmu.o emulate.o irq.o i8259.o pmu.o \
lapic.o ioapic.o preempt.o i8254.o coalesced_mmio.o irq_comm.o \
- eventfd.o compat-x86.o async_pf.o cpuid.o irqchip.o \
+ eventfd.o compat-x86.o async_pf.o cpuid.o irqchip.o vfio.o\
../external-module-compat.o
ifeq ($(CONFIG_IOMMU_API)$(CONFIG_PCI),yy)
kvm-objs += assigned-dev.o iommu.o
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
