summaryrefslogtreecommitdiffstats
path: root/include/linux/kvm.h
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2011-09-14 21:45:23 +0200
committerAvi Kivity <avi@redhat.com>2012-03-05 14:52:41 +0200
commit1022fc3d3bfaca09d5d6bfcc93a168de16840814 (patch)
treefee0d7dcceeb9704daf0bfc6b7e9a708f32b442e /include/linux/kvm.h
parente24ed81fedd551e80378be62fa0b0532480ea7d4 (diff)
downloadop-kernel-dev-1022fc3d3bfaca09d5d6bfcc93a168de16840814.zip
op-kernel-dev-1022fc3d3bfaca09d5d6bfcc93a168de16840814.tar.gz
KVM: PPC: Add support for explicit HIOR setting
Until now, we always set HIOR based on the PVR, but this is just wrong. Instead, we should be setting HIOR explicitly, so user space can decide what the initial HIOR value is - just like on real hardware. We keep the old PVR based way around for backwards compatibility, but once user space uses the SET_ONE_REG based method, we drop the PVR logic. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'include/linux/kvm.h')
-rw-r--r--include/linux/kvm.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index 4f7a9fb..acbe429 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -580,6 +580,7 @@ struct kvm_ppc_pvinfo {
#define KVM_CAP_PPC_SMT 64
#define KVM_CAP_PPC_RMA 65
#define KVM_CAP_MAX_VCPUS 66 /* returns max vcpus per vm */
+#define KVM_CAP_PPC_HIOR 67
#define KVM_CAP_PPC_PAPR 68
#define KVM_CAP_SW_TLB 69
#define KVM_CAP_ONE_REG 70
OpenPOWER on IntegriCloud