diff options
| author | Alexander Graf <agraf@suse.de> | 2014-07-14 12:33:08 -0400 |
|---|---|---|
| committer | Alexander Graf <agraf@suse.de> | 2014-07-28 09:23:17 -0400 |
| commit | 92b591a4c46b103ebd3fc0d03a084e1efd331253 (patch) | |
| tree | c42fdfa42d3ed67eb530977768d6f614024815ec /Documentation/virtual | |
| parent | 784aa3d7fb6f729c06d5836c9d9569f58e4d05ae (diff) | |
KVM: Allow KVM_CHECK_EXTENSION on the vm fd
The KVM_CHECK_EXTENSION is only available on the kvm fd today. Unfortunately
on PPC some of the capabilities change depending on the way a VM was created.
So instead we need a way to expose capabilities as VM ioctl, so that we can
see which VM type we're using (HV or PR). To enable this, add the
KVM_CHECK_EXTENSION ioctl to our vm ioctl portfolio.
Signed-off-by: Alexander Graf <agraf@suse.de>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation/virtual')
| -rw-r--r-- | Documentation/virtual/kvm/api.txt | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index 884f819e1908..8898caf8c090 100644 --- a/Documentation/virtual/kvm/api.txt +++ b/Documentation/virtual/kvm/api.txt | |||
| @@ -148,9 +148,9 @@ of banks, as set via the KVM_X86_SETUP_MCE ioctl. | |||
| 148 | 148 | ||
| 149 | 4.4 KVM_CHECK_EXTENSION | 149 | 4.4 KVM_CHECK_EXTENSION |
| 150 | 150 | ||
| 151 | Capability: basic | 151 | Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl |
| 152 | Architectures: all | 152 | Architectures: all |
| 153 | Type: system ioctl | 153 | Type: system ioctl, vm ioctl |
| 154 | Parameters: extension identifier (KVM_CAP_*) | 154 | Parameters: extension identifier (KVM_CAP_*) |
| 155 | Returns: 0 if unsupported; 1 (or some other positive integer) if supported | 155 | Returns: 0 if unsupported; 1 (or some other positive integer) if supported |
| 156 | 156 | ||
| @@ -160,6 +160,9 @@ receives an integer that describes the extension availability. | |||
| 160 | Generally 0 means no and 1 means yes, but some extensions may report | 160 | Generally 0 means no and 1 means yes, but some extensions may report |
| 161 | additional information in the integer return value. | 161 | additional information in the integer return value. |
| 162 | 162 | ||
| 163 | Based on their initialization different VMs may have different capabilities. | ||
| 164 | It is thus encouraged to use the vm ioctl to query for capabilities (available | ||
| 165 | with KVM_CAP_CHECK_EXTENSION_VM on the vm fd) | ||
| 163 | 166 | ||
| 164 | 4.5 KVM_GET_VCPU_MMAP_SIZE | 167 | 4.5 KVM_GET_VCPU_MMAP_SIZE |
| 165 | 168 | ||
