summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorPekka Enberg <penberg@kernel.org>2011-05-09 19:48:54 (GMT)
committerAvi Kivity <avi@redhat.com>2011-05-22 12:48:11 (GMT)
commit76d25402dfc972a135a656613736fe3602045a95 (patch)
tree2574a84c4437fd618011cc60f6227140cf4403fc /Documentation
parent8fa2206821953a50a3a02ea33fcfb3ced2fd9997 (diff)
downloadlinux-76d25402dfc972a135a656613736fe3602045a95.tar.xz
KVM: Add documentation for KVM_CAP_NR_VCPUS
Document KVM_CAP_NR_VCPUS that can be used by the userspace to determine maximum number of VCPUs it can create with the KVM_CREATE_VCPU ioctl. Cc: Avi Kivity <avi@redhat.com> Cc: Marcelo Tosatti <mtosatti@redhat.com> Cc: Jan Kiszka <jan.kiszka@web.de> Signed-off-by: Pekka Enberg <penberg@kernel.org> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/kvm/api.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index f64c41f..42542eb 100644
--- a/Documentation/kvm/api.txt
+++ b/Documentation/kvm/api.txt
@@ -175,7 +175,10 @@ Parameters: vcpu id (apic id on x86)
Returns: vcpu fd on success, -1 on error
This API adds a vcpu to a virtual machine. The vcpu id is a small integer
-in the range [0, max_vcpus).
+in the range [0, max_vcpus). You can use KVM_CAP_NR_VCPUS of the
+KVM_CHECK_EXTENSION ioctl() to determine the value for max_vcpus at run-time.
+If the KVM_CAP_NR_VCPUS does not exist, you should assume that max_vcpus is 4
+cpus max.
4.8 KVM_GET_DIRTY_LOG (vm ioctl)