qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Claudio Fontana <cfontana@suse.de>, Thomas Huth <thuth@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: Re: [PATCH] docs/s390: clarify even more that cpu-topology is KVM-only
Date: Thu, 14 Mar 2024 20:06:21 +0100	[thread overview]
Message-ID: <e892a83206380c9342f57e92562d3db4e4a125e8.camel@linux.ibm.com> (raw)
In-Reply-To: <20240314172218.16478-1-cfontana@suse.de>

On Thu, 2024-03-14 at 18:22 +0100, Claudio Fontana wrote:
> At least for now cpu-topology is implemented only for KVM.
> 
> We already say this, but this tries to be more explicit,
> and also show it in the examples.
> 
> This adds a new reference in the introduction that we can point to,
> whenever we need to reference accelerators and how to select them.
> 
> Signed-off-by: Claudio Fontana <cfontana@suse.de>

Reviewed-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Tested-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
(meaning I ran make html)

> ---
>  docs/system/introduction.rst       |  2 ++
>  docs/system/s390x/cpu-topology.rst | 14 ++++++++------
>  2 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/docs/system/introduction.rst b/docs/system/introduction.rst
> index 51ac132d6c..746707eb00 100644
> --- a/docs/system/introduction.rst
> +++ b/docs/system/introduction.rst
> @@ -1,6 +1,8 @@
>  Introduction
>  ============
>  
> +.. _Accelerators:
> +
>  Virtualisation Accelerators
>  ---------------------------
>  
> diff --git a/docs/system/s390x/cpu-topology.rst b/docs/system/s390x/cpu-topology.rst
> index 5133fdc362..ca344e273c 100644
> --- a/docs/system/s390x/cpu-topology.rst
> +++ b/docs/system/s390x/cpu-topology.rst
> @@ -25,17 +25,19 @@ monitor polarization changes, see ``docs/devel/s390-cpu-topology.rst``.
>  Prerequisites
>  -------------
>  
> -To use the CPU topology, you need to run with KVM on a s390x host that
> -uses the Linux kernel v6.0 or newer (which provide the so-called
> +To use the CPU topology, you currently need to choose the KVM accelerator.
> +See :ref:`Accelerators` for more details about accelerators and how to select them.
> +
> +The s390x host needs to use a Linux kernel v6.0 or newer (which provides the so-called
>  ``KVM_CAP_S390_CPU_TOPOLOGY`` capability that allows QEMU to signal the
>  CPU topology facility via the so-called STFLE bit 11 to the VM).
>  
>  Enabling CPU topology
>  ---------------------
>  
> -Currently, CPU topology is only enabled in the host model by default.
> +Currently, CPU topology is enabled by default only in the "host" cpu model.
>  
> -Enabling CPU topology in a CPU model is done by setting the CPU flag
> +Enabling CPU topology in another CPU model is done by setting the CPU flag
>  ``ctop`` to ``on`` as in:
>  
>  .. code-block:: bash
> @@ -132,7 +134,7 @@ In the following machine we define 8 sockets with 4 cores each.
>  
>  .. code-block:: bash
>  
> -  $ qemu-system-s390x -m 2G \
> +  $ qemu-system-s390x -accel kvm -m 2G \
>      -cpu gen16b,ctop=on \
>      -smp cpus=5,sockets=8,cores=4,maxcpus=32 \
>      -device host-s390x-cpu,core-id=14 \
> @@ -227,7 +229,7 @@ with vertical high entitlement.
>  
>  .. code-block:: bash
>  
> -  $ qemu-system-s390x -m 2G \
> +  $ qemu-system-s390x -accel kvm -m 2G \
>      -cpu gen16b,ctop=on \
>      -smp cpus=1,sockets=8,cores=4,maxcpus=32 \
>      \



  reply	other threads:[~2024-03-14 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 17:22 [PATCH] docs/s390: clarify even more that cpu-topology is KVM-only Claudio Fontana
2024-03-14 19:06 ` Nina Schoetterl-Glausch [this message]
2024-03-15  5:54 ` Philippe Mathieu-Daudé
2024-03-15  6:16 ` Thomas Huth

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=e892a83206380c9342f57e92562d3db4e4a125e8.camel@linux.ibm.com \
    --to=nsg@linux.ibm.com \
    --cc=cfontana@suse.de \
    --cc=iii@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.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).