From: Jonas Pfoh <pfoh@sec.in.tum.de>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: [PATCH kvm-kmod] fix undefined kvm_vfio_ops
Date: Fri, 24 Jan 2014 15:29:02 +0100 [thread overview]
Message-ID: <52E278AE.20505@sec.in.tum.de> (raw)
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 <pfoh@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
next reply other threads:[~2014-01-24 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 14:29 Jonas Pfoh [this message]
2014-01-24 15:14 ` [PATCH kvm-kmod] fix undefined kvm_vfio_ops Jan Kiszka
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=52E278AE.20505@sec.in.tum.de \
--to=pfoh@sec.in.tum.de \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
/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