From: Igor Mammedov Date: Fri, 11 Sep 2020 13:32:02 +0000 (-0400) Subject: smp: drop support for deprecated (invalid topologies) X-Git-Tag: v5.2.0-rc0~82^2~28 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b057f0961b10a5b052a81047d887a95ce206e00c;p=thirdparty%2Fqemu.git smp: drop support for deprecated (invalid topologies) it's was deprecated since 3.1 Support for invalid topologies is removed, the user must ensure that topologies described with -smp include all possible cpus, i.e. (sockets * cores * threads) == maxcpus or QEMU will exit with error. Signed-off-by: Igor Mammedov Acked-by: Message-Id: <20200911133202.938754-1-imammedo@redhat.com> Signed-off-by: Paolo Bonzini --- diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst index 716f6aa3157..da862201bab 100644 --- a/docs/system/deprecated.rst +++ b/docs/system/deprecated.rst @@ -646,6 +646,19 @@ 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*. + Block devices -------------