From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: KVM_CREATE_VCPU max vcpu ABI Date: Sat, 07 May 2011 13:12:25 +0200 Message-ID: <4DC52919.2040100@web.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFD66D513EB63CBA5DE929405" Cc: Avi Kivity , KVM General , Ingo Molnar , Asias He , Cyrill Gorcunov , Sasha Levin To: Pekka Enberg Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:42268 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754942Ab1EGLMb (ORCPT ); Sat, 7 May 2011 07:12:31 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFD66D513EB63CBA5DE929405 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-05-07 12:16, Pekka Enberg wrote: > Hi! >=20 > Documentation/kvm/api.txt says the following: >=20 > 4.6 KVM_CREATE_VCPU >=20 > Capability: basic > Architectures: all > Type: vm ioctl > Parameters: vcpu id (apic id on x86) > Returns: vcpu fd on success, -1 on error >=20 > This API adds a vcpu to a virtual machine. The vcpu id is a small in= teger > in the range [0, max_vcpus). >=20 > However, max_vcpus is not specified and I am unable to find ioctl() > which I could use to look it up. Is it specified somewhere? We can, of > course, attempt to create as many VCPUs as possible until > KVM_CREATE_VCPU returns EINVAL... Querying for KVM_CAP_NR_VCPUS returns this number (documented in the kvm header). Want to file a patch for adding a hint to the section above? Jan --------------enigFD66D513EB63CBA5DE929405 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FKR0ACgkQitSsb3rl5xTo+QCg8F0dkkvxVcjjZxX4VZQylvqD TjwAn1rIQZJ1nrjl3B2w8xP/Y6LmLldH =/MEI -----END PGP SIGNATURE----- --------------enigFD66D513EB63CBA5DE929405--