All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org,  qemu-devel@nongnu.org,
	 Richard Henderson <richard.henderson@linaro.org>,
	 Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Subject: Re: [PATCH v2 6/6] target/arm: Permit configurations with SME but not SVE
Date: Thu, 29 Jan 2026 15:59:27 +0000	[thread overview]
Message-ID: <877bt08l5s.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260129113455.1283266-7-peter.maydell@linaro.org> (Peter Maydell's message of "Thu, 29 Jan 2026 11:34:55 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> In commit f7767ca30179 ("target/arm: Disable SME if SVE is disabled")
> we added code that forces SME to be disabled if SVE is disabled.
> This was something we did in the run-up to a release to avoid an
> assertion failure in smcr_write() if the user disabled SVE on the
> 'max' CPU without disabling SME also.
>
> Now that we have corrected the code so that it doesn't assert
> in an SME-without-SVE setup, we can let users select it.
>
> This effectively reverts f7767ca30179.
>
> Note that this now means that command lines like "-cpu max,sve=off"
> which used to turn off SME and SVE will now give you a CPU with SME
> but not SVE.  This is permitted by our loose "max can always give you
> extra stuff" rules, but may be unexpected to users.  Mention this in
> the CPU property documentation.
>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>  docs/system/arm/cpu-features.rst | 10 ++++++++--
>  target/arm/cpu.c                 | 10 ----------
>  2 files changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
> index 37d5dfd15b..9d0c5731cc 100644
> --- a/docs/system/arm/cpu-features.rst
> +++ b/docs/system/arm/cpu-features.rst
> @@ -318,12 +318,18 @@ SVE CPU Property Parsing Semantics
>       provided an error will be generated.  To avoid this error, one must
>       enable at least one vector length prior to enabling SVE.
>  
> +  10) Disabling SVE does not automatically disable SME. If you want to
> +      disable both you must use ``sve=off,sme=off``. In particular,
> +      for the ``max`` CPU, ``sve=off`` alone will give you a CPU with
> +      SME only (and which therefore still has the SVE vector registers).
> +      Most users will want to disable both at once.
> +
>  SVE CPU Property Examples
>  -------------------------
>  
> -  1) Disable SVE::
> +  1) Disable SVE and SME::
>  
> -     $ qemu-system-aarch64 -M virt -cpu max,sve=off
> +     $ qemu-system-aarch64 -M virt -cpu max,sve=off,sme=off
>  
>    2) Implicitly enable all vector lengths for the ``max`` CPU type::


Reviewed-by: Alex Bennée <alex.bennee@linaro.org>

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      reply	other threads:[~2026-01-29 16:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 11:34 [PATCH v2 0/6] target/arm: Allow SME-only TCG CPUs Peter Maydell
2026-01-29 11:34 ` [PATCH v2 1/6] target/arm: Account for SME in aarch64_sve_narrow_vq() assertion Peter Maydell
2026-01-29 11:43   ` Philippe Mathieu-Daudé
2026-01-29 14:25   ` Alex Bennée
2026-02-02  5:21   ` Richard Henderson
2026-01-29 11:34 ` [PATCH v2 2/6] target/arm: Report correct vector width in gdbstub when SME present Peter Maydell
2026-01-29 11:44   ` Philippe Mathieu-Daudé
2026-01-29 14:36   ` Alex Bennée
2026-01-29 11:34 ` [PATCH v2 3/6] target/arm: Handle SME-only CPUs in sve_vqm1_for_el_sm() Peter Maydell
2026-01-29 14:56   ` Alex Bennée
2026-02-02  5:31   ` Richard Henderson
2026-01-29 11:34 ` [PATCH v2 4/6] target/arm: Handle SME-without-SVE on change of EL Peter Maydell
2026-01-29 11:47   ` Philippe Mathieu-Daudé
2026-01-29 14:57   ` Alex Bennée
2026-01-29 11:34 ` [PATCH v2 5/6] target/arm: Squash FEAT_SME_FA64 if FEAT_SVE is not present Peter Maydell
2026-02-02  5:32   ` Richard Henderson
2026-01-29 11:34 ` [PATCH v2 6/6] target/arm: Permit configurations with SME but not SVE Peter Maydell
2026-01-29 15:59   ` Alex Bennée [this message]

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=877bt08l5s.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.