From: Dario Faggioli <dfaggioli@suse.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "mst@redhat.com" <mst@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
"marcel.apfelbaum@gmail.com" <marcel.apfelbaum@gmail.com>,
"eduardo@habkost.net" <eduardo@habkost.net>
Subject: Re: [PATCH] pc: q35: Bump max_cpus to 1024
Date: Thu, 17 Nov 2022 18:04:28 +0000 [thread overview]
Message-ID: <bbbf1267cc26132e3d8627b7e2603c98cbe343c1.camel@suse.com> (raw)
In-Reply-To: <166869883160.17656.1212026522016331235.stgit@tumbleweed.Wayrath>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Well...
On Thu, 2022-11-17 at 16:27 +0100, Dario Faggioli wrote:
> Keep the old limit of 288 for machine versions 7.2 and earlier.
>
...At least, this was the idea...
> --- a/hw/i386/pc_q35.c
> +++ b/hw/i386/pc_q35.c
> @@ -386,6 +386,7 @@ static void
> pc_q35_7_1_machine_options(MachineClass *m)
> PCMachineClass *pcmc = PC_MACHINE_CLASS(m);
> pc_q35_7_2_machine_options(m);
> m->alias = NULL;
> + m->max_cpus = 288;
>
...But I managed to put this in the wrong function (xxx_7_1_yyy,
instead than xxx_7_2_yyyy)! :-/
Sorry about taht. I'll send a v2 (taking the feedback that I got to my
other email into account).
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-17 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 15:27 [PATCH] pc: q35: Bump max_cpus to 1024 Dario Faggioli
2022-11-17 18:04 ` Dario Faggioli [this message]
2022-11-18 9:34 ` Claudio Fontana
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=bbbf1267cc26132e3d8627b7e2603c98cbe343c1.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=eduardo@habkost.net \
--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).