From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: <qemu-devel@nongnu.org>
Cc: <marcel.apfelbaum@gmail.com>, <mst@redhat.com>,
<pbonzini@redhat.com>, <richard.henderson@linaro.org>,
<eduardo@habkost.net>, <jon.grimm@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [PATCH] pc: q35: Bump max_cpus to 512
Date: Wed, 4 May 2022 08:16:39 -0500 [thread overview]
Message-ID: <20220504131639.13570-1-suravee.suthikulpanit@amd.com> (raw)
This is the maximum number of vCPU supported by
the AMD x2APIC virtualization.
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
---
hw/i386/pc_q35.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
index 302288342a..e82b1c690d 100644
--- a/hw/i386/pc_q35.c
+++ b/hw/i386/pc_q35.c
@@ -357,7 +357,7 @@ static void pc_q35_machine_options(MachineClass *m)
machine_class_allow_dynamic_sysbus_dev(m, TYPE_INTEL_IOMMU_DEVICE);
machine_class_allow_dynamic_sysbus_dev(m, TYPE_RAMFB_DEVICE);
machine_class_allow_dynamic_sysbus_dev(m, TYPE_VMBUS_BRIDGE);
- m->max_cpus = 288;
+ m->max_cpus = 512;
}
static void pc_q35_7_1_machine_options(MachineClass *m)
--
2.25.1
next reply other threads:[~2022-05-04 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 13:16 Suravee Suthikulpanit [this message]
2022-05-09 7:12 ` [PATCH] pc: q35: Bump max_cpus to 512 Igor Mammedov
2022-05-09 11:41 ` Suthikulpanit, Suravee
2022-05-10 7:06 ` Igor Mammedov
2022-05-09 12:03 ` Daniel P. Berrangé
2022-05-10 7:03 ` Igor Mammedov
2022-05-10 8:14 ` Daniel P. Berrangé
2022-05-10 11:37 ` Igor Mammedov
2022-05-19 7:47 ` Julia Suvorova
2022-05-13 11:23 ` Michael S. Tsirkin
2022-05-19 6:53 ` Suravee Suthikulpanit
2022-05-19 12:37 ` Igor Mammedov
2022-05-19 13:43 ` Suravee Suthikulpanit
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=20220504131639.13570-1-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=eduardo@habkost.net \
--cc=jon.grimm@amd.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).