From 76d25402dfc972a135a656613736fe3602045a95 Mon Sep 17 00:00:00 2001 From: Pekka Enberg Date: Mon, 9 May 2011 22:48:54 +0300 Subject: 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 Cc: Marcelo Tosatti Cc: Jan Kiszka Signed-off-by: Pekka Enberg Signed-off-by: Avi Kivity --- Documentation/kvm/api.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'Documentation/kvm/api.txt') diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt index f64c41f8ba61..42542eb802ca 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) -- cgit v1.2.3