From: Avi Kivity <avi@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [PATCH] kvm: Add documentation for KVM_CAP_NR_VCPUS
Date: Mon, 09 May 2011 11:21:50 +0300 [thread overview]
Message-ID: <4DC7A41E.4050908@redhat.com> (raw)
In-Reply-To: <1304779352-8788-1-git-send-email-penberg@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.
prev parent reply other threads:[~2011-05-09 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 14:42 [PATCH] kvm: Add documentation for KVM_CAP_NR_VCPUS Pekka Enberg
2011-05-09 8:21 ` Avi Kivity [this message]
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=4DC7A41E.4050908@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).