summaryrefslogtreecommitdiffstats
path: root/drivers/kvm
diff options
context:
space:
mode:
authorAvi Kivity <avi@qumranet.com>2007-05-24 13:11:41 +0300
committerAvi Kivity <avi@qumranet.com>2007-07-16 12:05:51 +0300
commitcec9ad279b66793bee0b5009b7ca311060061efd (patch)
tree13608d474b725e3c155f2c4387b524743f60d4b8 /drivers/kvm
parent4267c41a458cd7d287dc8031468fc385c2f5b2c3 (diff)
downloadop-kernel-dev-cec9ad279b66793bee0b5009b7ca311060061efd.zip
op-kernel-dev-cec9ad279b66793bee0b5009b7ca311060061efd.tar.gz
KVM: Use CPU_DYING for disabling virtualization
Only at the CPU_DYING stage can we be sure that no user process will be scheduled onto the cpu and oops when trying to use virtualization extensions. Signed-off-by: Avi Kivity <avi@qumranet.com>
Diffstat (limited to 'drivers/kvm')
-rw-r--r--drivers/kvm/kvm_main.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 603e8ce..1b206f1 100644
--- a/drivers/kvm/kvm_main.c
+++ b/drivers/kvm/kvm_main.c
@@ -3004,8 +3004,8 @@ static int kvm_cpu_hotplug(struct notifier_block *notifier, unsigned long val,
int cpu = (long)v;
switch (val) {
- case CPU_DOWN_PREPARE:
- case CPU_DOWN_PREPARE_FROZEN:
+ case CPU_DYING:
+ case CPU_DYING_FROZEN:
case CPU_UP_CANCELED:
case CPU_UP_CANCELED_FROZEN:
printk(KERN_INFO "kvm: disabling virtualization on CPU%d\n",
OpenPOWER on IntegriCloud