qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Yanan Wang <wangyanan55@huawei.com>,
	qemu-devel@nongnu.org, libvir-list@redhat.com
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Andrew Jones" <drjones@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	wanghaibin.wang@huawei.com
Subject: Re: [PATCH v2 1/3] docs/about: Remove the duplicated doc
Date: Mon, 23 Aug 2021 07:26:57 +0200	[thread overview]
Message-ID: <6adb8073-2cd7-12c0-060d-33d5d78f3eee@redhat.com> (raw)
In-Reply-To: <20210823030005.165668-2-wangyanan55@huawei.com>

On 23/08/2021 05.00, Yanan Wang wrote:
> There are two places describing the same thing about deprecation
> of invalid topologies of -smp CLI, so remove the duplicated one.
> 
> Signed-off-by: Yanan Wang <wangyanan55@huawei.com>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> ---
>   docs/about/removed-features.rst | 13 -------------
>   1 file changed, 13 deletions(-)
> 
> diff --git a/docs/about/removed-features.rst b/docs/about/removed-features.rst
> index cbfa1a8e31..6a9c5bb484 100644
> --- a/docs/about/removed-features.rst
> +++ b/docs/about/removed-features.rst
> @@ -647,19 +647,6 @@ as ignored. Currently, users are responsible for making sure the backing storage
>   specified with ``-mem-path`` can actually provide the guest RAM configured with
>   ``-m`` and QEMU fails to start up if RAM allocation is unsuccessful.
>   
> -``-smp`` (invalid topologies) (removed 5.2)
> -'''''''''''''''''''''''''''''''''''''''''''
> -
> -CPU topology properties should describe whole machine topology including
> -possible CPUs.
> -
> -However, historically it was possible to start QEMU with an incorrect topology
> -where *n* <= *sockets* * *cores* * *threads* < *maxcpus*,
> -which could lead to an incorrect topology enumeration by the guest.
> -Support for invalid topologies is removed, the user must ensure
> -topologies described with -smp include all possible cpus, i.e.
> -*sockets* * *cores* * *threads* = *maxcpus*.
> -
>   ``-machine enforce-config-section=on|off`` (removed 5.2)
>   ''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>   
> 

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2021-08-23  5:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23  3:00 [PATCH v2 0/3] docs/about: some documentation clean-up/fix Yanan Wang
2021-08-23  3:00 ` [PATCH v2 1/3] docs/about: Remove the duplicated doc Yanan Wang
2021-08-23  5:26   ` Thomas Huth [this message]
2021-08-23  9:00   ` Andrew Jones
2021-08-23  3:00 ` [PATCH v2 2/3] docs/about: Unify the subject format Yanan Wang
2021-08-23  5:29   ` Thomas Huth
2021-08-23  9:02   ` Andrew Jones
2021-08-23  3:00 ` [PATCH v2 3/3] docs/about: Add the missing release record in the subject Yanan Wang
2021-08-23  5:30   ` Thomas Huth
2021-08-23  9:03   ` Andrew Jones

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=6adb8073-2cd7-12c0-060d-33d5d78f3eee@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=drjones@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wanghaibin.wang@huawei.com \
    --cc=wangyanan55@huawei.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).