From: Zhao Liu <zhao1.liu@linux.intel.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Zhao Liu <zhao1.liu@intel.com>,
Ani Sinha <anisinha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PATCH-for-9.0?] docs: i386: pc: Update maximum CPU numbers for PC Q35
Date: Fri, 12 Apr 2024 19:48:53 +0800 [thread overview]
Message-ID: <ZhkfpQUwRMXDUSsp@intel.com> (raw)
In-Reply-To: <305d659b-d4d6-4681-bdad-cd869e552333@linaro.org>
Hi Philippe,
On Fri, Apr 12, 2024 at 11:57:35AM +0200, Philippe Mathieu-Daudé wrote:
> Date: Fri, 12 Apr 2024 11:57:35 +0200
> From: Philippe Mathieu-Daudé <philmd@linaro.org>
> Subject: Re: [PATCH-for-9.0?] docs: i386: pc: Update maximum CPU numbers
> for PC Q35
>
> > -SMP is supported with up to 255 CPUs.
> > +SMP is supported with up to 255 CPUs (and 4096 CPUs for PC Q35 machine).
>
> This comment is not accurate since a while, IIUC:
>
> Up to q35-2.7: 255
> q35-2.8: 288
> q35-8.0+: 1024
> q35-9.0: 4096
Yes, I think there should be no need to mention older versions here?
Since the Q35's 4096 CPUs change will be stated in the v9.0 release, I
doubt we should synchronize the doc update (so I added the "for-v9.0?"
tag to throw this question out).
Thanks,
Zhao
next prev parent reply other threads:[~2024-04-12 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 8:53 [PATCH-for-9.0?] docs: i386: pc: Update maximum CPU numbers for PC Q35 Zhao Liu
2024-04-12 9:57 ` Philippe Mathieu-Daudé
2024-04-12 11:48 ` Zhao Liu [this message]
2024-06-02 13:30 ` Michael S. Tsirkin
2024-06-03 17:31 ` Philippe Mathieu-Daudé
2024-06-03 17:39 ` Daniel P. Berrangé
2024-06-04 8:59 ` Zhao Liu
2024-06-04 8:49 ` Daniel P. Berrangé
2024-06-04 8:54 ` Zhao Liu
2024-06-04 9:29 ` Philippe Mathieu-Daudé
2024-06-04 16:12 ` Zhao Liu
2024-06-02 13:28 ` Michael S. Tsirkin
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=ZhkfpQUwRMXDUSsp@intel.com \
--to=zhao1.liu@linux.intel.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.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).