diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2014-09-24 13:02:46 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2014-09-24 14:06:36 +0200 |
| commit | 3c3c29fd0d7cddc32862c350d0700ce69953e3bd (patch) | |
| tree | 69a96edbbe94bb5ab6ad6c3f239b72eda13f7593 /virt/kvm/vfio.c | |
| parent | 29f1b65b5984c1e35e2d60d1416d03cee0b91ee2 (diff) | |
| download | linux-3c3c29fd0d7cddc32862c350d0700ce69953e3bd.tar.gz linux-3c3c29fd0d7cddc32862c350d0700ce69953e3bd.tar.bz2 linux-3c3c29fd0d7cddc32862c350d0700ce69953e3bd.zip | |
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 <will.deacon@arm.com>
Cc: Gleb Natapov <gleb@kernel.org>
Cc: Alex Williamson <Alex.Williamson@redhat.com>
Fixes: 80ce1639727e9d38729c34f162378508c307ca25
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt/kvm/vfio.c')
| -rw-r--r-- | virt/kvm/vfio.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/virt/kvm/vfio.c b/virt/kvm/vfio.c index bb11b36ee8a2..281e7cf2b8e5 100644 --- a/virt/kvm/vfio.c +++ b/virt/kvm/vfio.c @@ -18,6 +18,7 @@ #include <linux/slab.h> #include <linux/uaccess.h> #include <linux/vfio.h> +#include "vfio.h" struct kvm_vfio_group { struct list_head node; @@ -278,8 +279,7 @@ static int kvm_vfio_create(struct kvm_device *dev, u32 type) return 0; } -static int __init kvm_vfio_ops_init(void) +int kvm_vfio_ops_init(void) { return kvm_register_device_ops(&kvm_vfio_ops, KVM_DEV_TYPE_VFIO); } -module_init(kvm_vfio_ops_init); |