From: Eduardo Habkost <ehabkost@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Lan Tianyu <tianyu.lan@intel.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] x86: Increase max vcpu number to 352
Date: Fri, 11 Aug 2017 08:51:14 -0300 [thread overview]
Message-ID: <20170811115114.GD3108@localhost.localdomain> (raw)
In-Reply-To: <20170810180838.GS2547@char.us.oracle.com>
On Thu, Aug 10, 2017 at 02:08:38PM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Aug 09, 2017 at 11:58:20PM -0400, Lan Tianyu wrote:
> > Intel Xeon phi chip will support 352 logical threads. For HPC
> > usage case, it will create a huge VM with vcpus number as same as host
> > cpus. This patch is to increase max vcpu number to 352.
>
> There is this ioctl called KVM_CAP_MAX_VCPUS. Why not use that?
>
> Oh wait, this is generic code. Perhaps there is a way to make
> this more abstract? Where this information is provided via
> an function to which various accelerators register?
We already check KVM_CAP_MAX_VCPUS, see kvm-all.c:kvm_init().
MachineClass::max_cpus is a limit defined at compile time, based
on the limitations of the existing QEMU machine/device code.
--
Eduardo
next prev parent reply other threads:[~2017-08-11 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 3:58 [Qemu-devel] [PATCH] x86: Increase max vcpu number to 352 Lan Tianyu
2017-08-10 18:08 ` Konrad Rzeszutek Wilk
2017-08-11 11:51 ` Eduardo Habkost [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-10 10:08 Lan Tianyu
2017-08-10 10:26 ` Daniel P. Berrange
2017-08-10 11:02 ` Lan Tianyu
2017-08-10 12:41 ` Radim Krčmář
2017-08-10 18:16 ` Eduardo Habkost
2017-08-10 19:22 ` Radim Krčmář
2017-08-11 6:07 ` Lan Tianyu
2017-08-10 12:13 ` Paolo Bonzini
2017-08-10 13:52 ` Daniel P. Berrange
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=20170811115114.GD3108@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=tianyu.lan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.