path: root/virt/kvm/vfio.h
diff options
authorPaolo Bonzini <>2014-09-24 13:02:46 +0200
committerPaolo Bonzini <>2014-09-24 14:06:36 +0200
commit3c3c29fd0d7cddc32862c350d0700ce69953e3bd (patch)
tree69a96edbbe94bb5ab6ad6c3f239b72eda13f7593 /virt/kvm/vfio.h
parent29f1b65b5984c1e35e2d60d1416d03cee0b91ee2 (diff)
kvm-vfio: do not use module_init
/me got confused between the kernel and QEMU. In the kernel, you can only have one module_init function, and it will prevent unloading the module unless you also have the corresponding module_exit function. So, commit 80ce1639727e (KVM: VFIO: register kvm_device_ops dynamically, 2014-09-02) broke unloading of the kvm module, by adding a module_init function and no module_exit. Repair it by making kvm_vfio_ops_init weak, and checking it in kvm_init. Cc: Will Deacon <> Cc: Gleb Natapov <> Cc: Alex Williamson <> Fixes: 80ce1639727e9d38729c34f162378508c307ca25 Signed-off-by: Paolo Bonzini <>
Diffstat (limited to 'virt/kvm/vfio.h')
1 files changed, 13 insertions, 0 deletions
diff --git a/virt/kvm/vfio.h b/virt/kvm/vfio.h
new file mode 100644
index 000000000000..92eac75d6b62
--- /dev/null
+++ b/virt/kvm/vfio.h
@@ -0,0 +1,13 @@
+#ifndef __KVM_VFIO_H
+#define __KVM_VFIO_H
+int kvm_vfio_ops_init(void);
+static inline int kvm_vfio_ops_init(void)
+ return 0;