From: Lan Tianyu <tianyu.lan@intel.com>
To: qemu-devel@nongnu.org
Cc: Lan Tianyu <tianyu.lan@intel.com>,
mst@redhat.com, pbonzini@redhat.com, rth@twiddle.net,
ehabkost@redhat.com, berrange@redhat.com, rkrcmar@redhat.com
Subject: [Qemu-devel] [PATCH v3 2/2] x86: Increase max vcpu number to 8192
Date: Tue, 15 Aug 2017 20:06:19 -0400 [thread overview]
Message-ID: <1502841979-6233-2-git-send-email-tianyu.lan@intel.com> (raw)
In-Reply-To: <1502841979-6233-1-git-send-email-tianyu.lan@intel.com>
For HPC usage case, it will create a huge VM with vcpus number as same as host
cpus and this requires more vcpus support in a single VM. This patch is to
increase max vcpu number from 288 to 8192 which is current default maximum cpu
number for Linux kernel.
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
---
hw/i386/pc_q35.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
index b469d05..3468f5a 100644
--- a/hw/i386/pc_q35.c
+++ b/hw/i386/pc_q35.c
@@ -299,7 +299,7 @@ static void pc_q35_machine_options(MachineClass *m)
m->default_display = "std";
m->no_floppy = 1;
m->has_dynamic_sysbus = true;
- m->max_cpus = 288;
+ m->max_cpus = 8192;
}
static void pc_q35_2_11_machine_options(MachineClass *m)
@@ -314,6 +314,7 @@ static void pc_q35_2_10_machine_options(MachineClass *m)
{
pc_q35_2_11_machine_options(m);
m->alias = NULL;
+ m->max_cpus = 288;
m->numa_auto_assign_ram = numa_legacy_auto_assign_ram;
SET_MACHINE_COMPAT(m, PC_COMPAT_2_10);
}
--
1.8.3.1
next prev parent reply other threads:[~2017-08-16 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 0:06 [Qemu-devel] [PATCH v3 1/2] pc: add 2.11 machine type Lan Tianyu
2017-08-16 0:06 ` Lan Tianyu [this message]
2017-08-18 19:01 ` Eduardo Habkost
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=1502841979-6233-2-git-send-email-tianyu.lan@intel.com \
--to=tianyu.lan@intel.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=rth@twiddle.net \
/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).