From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: [PULL 1/6] docs/about: Remove the duplicated doc
Date: Wed, 25 Aug 2021 13:00:13 +0200 [thread overview]
Message-ID: <20210825110018.100913-2-thuth@redhat.com> (raw)
In-Reply-To: <20210825110018.100913-1-thuth@redhat.com>
From: Yanan Wang <wangyanan55@huawei.com>
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>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20210823030005.165668-2-wangyanan55@huawei.com>
Signed-off-by: Thomas Huth <thuth@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)
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
--
2.27.0
next prev parent reply other threads:[~2021-08-25 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 11:00 [PULL 0/6] documentation updates Thomas Huth
2021-08-25 11:00 ` Thomas Huth [this message]
2021-08-25 11:00 ` [PULL 2/6] docs/about: Unify the subject format Thomas Huth
2021-08-25 11:00 ` [PULL 3/6] docs/about: Add the missing release record in the subject Thomas Huth
2021-08-25 11:00 ` [PULL 4/6] docs/about/removed-features: Move some CLI options to the right location Thomas Huth
2021-08-25 11:00 ` [PULL 5/6] docs: split the CI docs into two files Thomas Huth
2021-08-30 13:33 ` Philippe Mathieu-Daudé
2021-08-30 16:02 ` Thomas Huth
2021-08-30 21:15 ` Philippe Mathieu-Daudé
2021-08-31 5:07 ` Thomas Huth
2021-08-25 11:00 ` [PULL 6/6] docs: make sphinx-build be quiet by default Thomas Huth
2021-08-25 20:09 ` [PULL 0/6] documentation updates Peter Maydell
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=20210825110018.100913-2-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).