summaryrefslogtreecommitdiffstats
path: root/arch/powerpc
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2010-08-17 11:41:44 +0200
committerAvi Kivity <avi@redhat.com>2010-10-24 10:52:15 +0200
commitad0873763a83e7b31ba87a85ec2027dd6a9d7b55 (patch)
treeefc7e87eb5026732633f655d7270b66c7f586ec1 /arch/powerpc
parentdf08bd10266ce6132278f6b4ddc4bb0a12330b56 (diff)
downloadop-kernel-dev-ad0873763a83e7b31ba87a85ec2027dd6a9d7b55.zip
op-kernel-dev-ad0873763a83e7b31ba87a85ec2027dd6a9d7b55.tar.gz
KVM: PPC: Force enable nap on KVM
There are some heuristics in the PPC power management code that try to find out if the particular hardware we're running on supports proper power management or just hangs the machine when going into nap mode. Since we know that KVM is safe with nap, let's force enable it in the PV code once we're certain that we are on a KVM VM. Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'arch/powerpc')
-rw-r--r--arch/powerpc/kernel/kvm.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/arch/powerpc/kernel/kvm.c b/arch/powerpc/kernel/kvm.c
index 48a0338..669d989 100644
--- a/arch/powerpc/kernel/kvm.c
+++ b/arch/powerpc/kernel/kvm.c
@@ -582,6 +582,9 @@ static int __init kvm_guest_init(void)
if (kvm_para_has_feature(KVM_FEATURE_MAGIC_PAGE))
kvm_use_magic_page();
+ /* Enable napping */
+ powersave_nap = 1;
+
free_tmp:
kvm_free_tmp();
OpenPOWER on IntegriCloud