On Mon, Jan 08, 2024 at 20:26:09 +0100, Andrea Bolognani wrote:
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
docs/formatcaps.rst | 2 +-
docs/formatdomain.rst | 18 ++++++++++--------
2 files changed, 11 insertions(+), 9 deletions(-)
[...]
@@ -1579,12 +1579,14 @@ In case no restrictions need to be put on CPU model and its
features, a simpler
``topology``
The ``topology`` element specifies requested topology of virtual CPU provided
to the guest.
- Four attributes, ``sockets``, ``dies`` (:since:`Since 6.1.0`), ``cores``, and
- ``threads``, accept non-zero positive integer values.
+ Five attributes, ``sockets``, ``dies`` (:since:`Since 6.1.0`), ``clusters``
+ (:since:`Since 10.0.0`), ``cores``, and ``threads``, accept non-zero positive
Don't forget to increment the version.
+ integer values.
They refer to the total number of CPU sockets, number of dies per socket,
- number of cores per die, and number of threads per core, respectively.
- The ``dies`` attribute is optional and will default to 1 if omitted, while
- the other attributes are all mandatory.
+ number of clusters per die, number of cores per cluster, and number of
+ threads per core, respectively.
+ The ``dies`` and ``clusters`` attributes are optional and will default to 1
+ if omitted, while the other attributes are all mandatory.
Hypervisors may require that the maximum number of vCPUs specified
by the ``cpus`` element equals to the number of vcpus resulting from the
topology.
--
2.43.0
_______________________________________________
Devel mailing list -- devel(a)lists.libvirt.org
To unsubscribe send an email to devel-leave(a)lists.libvirt.org
Reviewed-by: Peter Krempa <pkrempa(a)redhat.com>