qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org
Subject: [PATCH v2 0/3] target/arm: Add sve-default-vector-length cpu property
Date: Fri, 23 Jul 2021 10:33:41 -1000	[thread overview]
Message-ID: <20210723203344.968563-1-richard.henderson@linaro.org> (raw)

This is intended to resolve #482.

Changes for v2:
  * Split out length bounding fix to new patch.
  * Use byte units for sve-default-vector-length.
  * Support undocumented -1 "maximum".
  * Add documentation.


r~


Richard Henderson (3):
  target/arm: Correctly bound length in sve_zcr_get_valid_len
  target/arm: Export aarch64_sve_zcr_get_valid_len
  target/arm: Add sve-default-vector-length cpu property

 docs/system/arm/cpu-features.rst | 11 ++++++
 target/arm/cpu.h                 |  5 +++
 target/arm/internals.h           | 10 ++++++
 target/arm/cpu.c                 | 14 ++++++--
 target/arm/cpu64.c               | 60 ++++++++++++++++++++++++++++++++
 target/arm/helper.c              |  8 +++--
 6 files changed, 103 insertions(+), 5 deletions(-)

-- 
2.25.1



             reply	other threads:[~2021-07-23 20:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 20:33 Richard Henderson [this message]
2021-07-23 20:33 ` [PATCH v2 1/3] target/arm: Correctly bound length in sve_zcr_get_valid_len Richard Henderson
2021-07-26 10:57   ` Peter Maydell
2021-07-23 20:33 ` [PATCH v2 2/3] target/arm: Export aarch64_sve_zcr_get_valid_len Richard Henderson
2021-07-26 10:57   ` Peter Maydell
2021-07-23 20:33 ` [PATCH v2 3/3] target/arm: Add sve-default-vector-length cpu property Richard Henderson
2021-07-26 11:07   ` Peter Maydell
2021-07-26 14:59   ` Andrew Jones
2021-07-26 18:33     ` Richard Henderson
2021-07-26 18:40       ` Andrew Jones
2021-07-26 19:31       ` Peter Maydell
2021-07-26 12:42 ` [PATCH v2 0/3] " Peter Maydell
2021-07-26 15:00   ` Andrew Jones
2021-07-26 15:41     ` 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=20210723203344.968563-1-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=qemu-arm@nongnu.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).