From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] docs: i386: pc: Avoid mentioning limit of maximum vCPUs
Date: Thu, 6 Jun 2024 09:44:44 +0100 [thread overview]
Message-ID: <ZmF2_Mx4kUOcGn00@redhat.com> (raw)
In-Reply-To: <20240606085436.2028900-1-zhao1.liu@intel.com>
On Thu, Jun 06, 2024 at 04:54:36PM +0800, Zhao Liu wrote:
> Different versions of PC machine support different maximum vCPUs, and
> even different features have limits on the maximum number of vCPUs (
> For example, if x2apic is not enabled in the TCG case, the maximum of
> 255 vCPUs are supported).
>
> It is difficult to list the maximum vCPUs under all restrictions. Thus,
> to avoid confusion, avoid mentioning specific maximum vCPU number
> limitations here.
>
> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
> ---
> docs/system/target-i386-desc.rst.inc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-06-06 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 8:54 [PATCH] docs: i386: pc: Avoid mentioning limit of maximum vCPUs Zhao Liu
2024-06-06 8:44 ` Daniel P. Berrangé [this message]
2024-06-06 9:02 ` Paolo Bonzini
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=ZmF2_Mx4kUOcGn00@redhat.com \
--to=berrange@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.