From: Jan Kiszka <jan.kiszka@web.de>
To: Pekka Enberg <penberg@kernel.org>
Cc: Avi Kivity <avi@redhat.com>, KVM General <kvm@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Asias He <asias.hejun@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: KVM_CREATE_VCPU max vcpu ABI
Date: Sat, 07 May 2011 13:12:25 +0200 [thread overview]
Message-ID: <4DC52919.2040100@web.de> (raw)
In-Reply-To: <BANLkTin6HzjzCkb6cVux0+mkwT8GxwLG1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On 2011-05-07 12:16, Pekka Enberg wrote:
> Hi!
>
> Documentation/kvm/api.txt says the following:
>
> 4.6 KVM_CREATE_VCPU
>
> Capability: basic
> Architectures: all
> Type: vm ioctl
> 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).
>
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-05-07 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 10:16 KVM_CREATE_VCPU max vcpu ABI Pekka Enberg
2011-05-07 11:12 ` Jan Kiszka [this message]
2011-05-07 14:48 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DC52919.2040100@web.de \
--to=jan.kiszka@web.de \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox