From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: [PATCH v2] kvm: Add documentation for KVM_CAP_NR_VCPUS Date: Mon, 9 May 2011 22:48:54 +0300 Message-ID: <1304970534-7824-1-git-send-email-penberg@kernel.org> Cc: Pekka Enberg , Avi Kivity , Marcelo Tosatti , Jan Kiszka To: kvm@vger.kernel.org Return-path: Received: from filtteri1.pp.htv.fi ([213.243.153.184]:42726 "EHLO filtteri1.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753617Ab1EITs4 (ORCPT ); Mon, 9 May 2011 15:48:56 -0400 Sender: kvm-owner@vger.kernel.org List-ID: 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 --- Documentation/kvm/api.txt | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt index 9bef4e4..533da6b 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) -- 1.7.0.4