Avi Kivity a4c0364be3 KVM: Explicity initialize cpus_hardware_enabled ... Under CONFIG_MAXSMP, cpus_hardware_enabled is allocated from the heap and not statically initialized. This causes a crash on reboot when kvm thinks vmx is enabled on random nonexistent cpus and accesses nonexistent percpu lists. Fix by explicitly clearing the variable. Cc: stable@kernel.org Reported-and-tested-by: Yinghai Lu <yinghai@kernel.org> Signed-off-by: Avi Kivity <avi@redhat.com>		2009-06-08 10:50:46 +03:00
..
coalesced_mmio.c	KVM: Add coalesced MMIO support (common part)	2008-07-20 12:42:31 +03:00
coalesced_mmio.h	KVM: Add coalesced MMIO support (common part)	2008-07-20 12:42:31 +03:00
ioapic.c	KVM: Report IRQ injection status to userspace.	2009-03-24 11:03:11 +02:00
ioapic.h	KVM: Report IRQ injection status to userspace.	2009-03-24 11:03:11 +02:00
iodev.h	KVM: kvm_io_device: extend in_range() to manage len and write attribute	2008-07-20 12:42:30 +03:00
iommu.c	KVM: Fix assigned devices circular locking dependency	2009-02-15 02:47:39 +02:00
irq_comm.c	KVM: fix sparse warnings: Should it be static?	2009-03-24 11:03:14 +02:00
kvm_main.c	KVM: Explicity initialize cpus_hardware_enabled	2009-06-08 10:50:46 +03:00
kvm_trace.c	KVM: Prevent trace call into unloaded module text	2008-12-31 16:55:04 +02:00