From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>, Alexander Graf <agraf@suse.de>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 3/3] kvm-s390: implement KVM_CAP_MAX_VCPUS
Date: Mon, 30 Apr 2012 22:00:41 -0300 [thread overview]
Message-ID: <20120501010041.GA9609@amt.cnet> (raw)
In-Reply-To: <20120501005147.GA9621@amt.cnet>
On Mon, Apr 30, 2012 at 09:51:47PM -0300, Marcelo Tosatti wrote:
> On Tue, Apr 24, 2012 at 04:01:40PM +0300, Avi Kivity wrote:
> > On 04/24/2012 03:47 PM, Christian Borntraeger wrote:
> > > > btw, a better place might be in kvm_devel_ioctl_check_extension_generic().
> > >
> > > Possibly yes. Dont know if there are architecture specific reasons to use
> > > something different than KVM_MAX_VCPUS.
> >
> > Okay, I'll fold the implementations unless something prevents it (unlikely).
>
> KVM_CAP_NR_VCPUS = "recommended max_vcpus"
> KVM_CAP_MAX_VCPUS = "maximum possible value for max_vcpus"
>
> (commit 8c3ba334f8588e1d5)
>
> CAP_NR_VCPUS is architecture dependent (depends on state of scability,
> testing, etc).
Both KVM_CAP_MAX_VCPUS and KVM_CAP_NR_VCPUS are architecture dependent.
Christian, you probably want to implement both (skipping this one
patch), applied remainder, thanks.
next prev parent reply other threads:[~2012-05-01 1:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 7:24 [PATCH 0/3] Fixes and feature for kvm-s390 Christian Borntraeger
2012-04-24 7:24 ` [PATCH 1/3] kvm-s390: Implement the directed yield (diag 9c) hypervisor call for KVM Christian Borntraeger
2012-04-24 12:04 ` Avi Kivity
2012-04-24 12:44 ` Christian Borntraeger
2012-04-24 12:55 ` [PATCH 1/3v2] " Christian Borntraeger
2012-04-24 13:06 ` Avi Kivity
2012-04-24 15:47 ` Christian Borntraeger
2012-04-24 16:15 ` Avi Kivity
2012-04-24 16:21 ` Christian Borntraeger
2012-04-24 16:22 ` Avi Kivity
2012-04-25 13:30 ` [PATCH 0/2] rework kvm_vcpu_on_spin Christian Borntraeger
2012-04-25 13:30 ` [PATCH 1/2] kvm-s390: Implement the directed yield (diag 9c) hypervisor call for KVM Christian Borntraeger
2012-04-26 12:06 ` Alexander Graf
2012-04-26 12:19 ` Christian Borntraeger
2012-04-26 12:26 ` Alexander Graf
2012-04-25 13:30 ` [PATCH 2/2] kvm-s390: use kvm_vcpu_on_spin for diag 0x44 Christian Borntraeger
2012-04-29 11:10 ` [PATCH 0/2] rework kvm_vcpu_on_spin Avi Kivity
2012-06-06 12:55 ` trace points and ABI Christian Borntraeger
2012-06-06 13:12 ` Avi Kivity
2012-04-24 7:24 ` [PATCH 2/3] kvm-s390: Handle sckpf instruction Christian Borntraeger
2012-04-24 7:24 ` [PATCH 3/3] kvm-s390: implement KVM_CAP_MAX_VCPUS Christian Borntraeger
2012-04-24 12:06 ` Avi Kivity
2012-04-24 12:47 ` Christian Borntraeger
2012-04-24 13:01 ` Avi Kivity
2012-05-01 0:51 ` Marcelo Tosatti
2012-05-01 1:00 ` Marcelo Tosatti [this message]
2012-05-02 8:50 ` [PATCH 0/1] Updated Patch for NR/MAX VCPU on s390 Christian Borntraeger
2012-05-02 8:50 ` [PATCH 1/1] kvm-s390x: implement KVM_CAP_NR/MAX_VCPUS Christian Borntraeger
2012-05-02 21:36 ` Marcelo Tosatti
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=20120501010041.GA9609@amt.cnet \
--to=mtosatti@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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