From: Igor Mammedov <imammedo@redhat.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, marcel.apfelbaum@gmail.com,
pbonzini@redhat.com, richard.henderson@linaro.org,
eduardo@habkost.net, jon.grimm@amd.com
Subject: Re: [PATCH] pc: q35: Bump max_cpus to 512
Date: Thu, 19 May 2022 14:37:54 +0200 [thread overview]
Message-ID: <20220519143754.42b200d4@redhat.com> (raw)
In-Reply-To: <2cec4bba-4400-ae74-231e-c064f03df691@amd.com>
On Thu, 19 May 2022 13:53:49 +0700
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> wrote:
> On 5/13/22 6:23 PM, Michael S. Tsirkin wrote:
> > On Mon, May 09, 2022 at 09:12:49AM +0200, Igor Mammedov wrote:
> >> On Wed, 4 May 2022 08:16:39 -0500
> >> Suravee Suthikulpanit<suravee.suthikulpanit@amd.com> wrote:
> >>
> >>> 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;
> >> Maybe we should bump it to KVM VCPU maximum,
> >> and make sure we error out if asked for combination of
> >> hardware/irqchip is not usable.
> >
> > So what happens if one does 710 and then tries to use AMD x2APIC?
> > We'd like that to error out, right?
> >
>
> Since the AMD SVM x2AVIC can support only upto 512 vCPUs,
> KVM would return error when QEMU tries to create more than 512 vcpus
> in the following call-path:
>
> kvm_vm_ioctl_create_vcpu
> kvm_arch_vcpu_create
> svm_vcpu_create
> avic_init_vcpu
what is actual error message that end user will get from that failure?
> Also, I tried to find a way to get the KVM VCPU max value via KVM_CAP_MAX_VCPUS ioctl,
> but the accel/kvm/kvm-all.c:kvm_init() is called later than hw/core/machine-smp.c:
> machine_parse_smp_config(), where it checks the specified QEMU -smp option.
>
> So, if there is no objection, I will send out a patch to change m->max_cpus = 1024
> to match current KVM limit.
>
> Best Regards,
> Suravee
>
next prev parent reply other threads:[~2022-05-19 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 13:16 [PATCH] pc: q35: Bump max_cpus to 512 Suravee Suthikulpanit
2022-05-09 7:12 ` 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 [this message]
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=20220519143754.42b200d4@redhat.com \
--to=imammedo@redhat.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 \
--cc=suravee.suthikulpanit@amd.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;
as well as URLs for NNTP newsgroup(s).