From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] kvm: Add documentation for KVM_CAP_NR_VCPUS
Date: Mon, 09 May 2011 11:21:50 +0300
Message-ID: <4DC7A41E.4050908@redhat.com>
References: <1304779352-8788-1-git-send-email-penberg@kernel.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	Jan Kiszka <jan.kiszka@web.de>
To: Pekka Enberg <penberg@kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:8747 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753413Ab1EIIWA (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 9 May 2011 04:22:00 -0400
In-Reply-To: <1304779352-8788-1-git-send-email-penberg@kernel.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 05/07/2011 05:42 PM, Pekka Enberg wrote:
> 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.
>

This capability was added in 2.6.26; so the documentation should state 
that if the capability is not available the user should assume 4 cpus 
max (the limit at the time).

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.