From: Lan Tianyu <tianyu.lan@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Lan Tianyu <tianyu.lan@intel.com>,
pbonzini@redhat.com, rkrcmar@redhat.com, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] KVM/x86: Increase max vcpu number to 352
Date: Thu, 10 Aug 2017 18:00:59 +0800 [thread overview]
Message-ID: <1502359259-24966-1-git-send-email-tianyu.lan@intel.com> (raw)
Intel Xeon phi chip will support 352 logical threads. For HPC usage
case, it will create a huge VM with vcpu number as same as host cpus. This
patch is to increase max vcpu number to 352.
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
---
arch/x86/include/asm/kvm_host.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index 87ac4fb..2cdc043 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/asm/kvm_host.h
@@ -35,7 +35,7 @@
#include <asm/asm.h>
#include <asm/kvm_page_track.h>
-#define KVM_MAX_VCPUS 288
+#define KVM_MAX_VCPUS 352
#define KVM_SOFT_MAX_VCPUS 240
#define KVM_MAX_VCPU_ID 1023
#define KVM_USER_MEM_SLOTS 509
--
1.8.3.1
next reply other threads:[~2017-08-10 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 10:00 Lan Tianyu [this message]
[not found] ` <20170810175056.GR2547@char.us.oracle.com>
2017-08-11 7:49 ` Lan Tianyu
2017-08-11 8:11 ` David Hildenbrand
2017-08-11 13:00 ` Radim Krčmář
2017-08-11 19:35 ` Konrad Rzeszutek Wilk
2017-08-15 3:00 ` Lan Tianyu
2017-08-15 14:10 ` Konrad Rzeszutek Wilk
2017-08-15 16:13 ` Radim Krčmář
2017-08-18 13:57 ` Konrad Rzeszutek Wilk
2017-08-21 15:44 ` Radim Krčmář
2017-08-16 3:07 ` Lan Tianyu
2017-08-18 14:20 ` Konrad Rzeszutek Wilk
2017-08-15 14:20 ` Radim Krčmář
2017-08-11 22:47 ` Denys Vlasenko
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=1502359259-24966-1-git-send-email-tianyu.lan@intel.com \
--to=tianyu.lan@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome