From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, thuth@redhat.com, david@redhat.com,
philmd@linaro.org, mjt@tls.msk.ru
Subject: [PATCH 0/2] tcg/s390x: Fix chacha20-s390
Date: Thu, 18 Jan 2024 08:36:44 +1100 [thread overview]
Message-ID: <20240117213646.159697-1-richard.henderson@linaro.org> (raw)
So it turns out the regression exposed by "Optimize env memory operations"
is caused by an s390x host encoding error. This is the first time that we
have had sufficient register pressure to use more than a few vector
registers at the same time.
As such, the testcase itself is interesting, since nothing else in our
testsuite generates translation blocks with quite so many vector insns
with more than 16 simultaneously live values.
r~
Richard Henderson (2):
tcg/s390x: Fix encoding of VRIc, VRSa, VRSc insns
tests/tcg/s390x: Import linux tools/testing/crypto/chacha20-s390
tests/tcg/s390x/chacha.c | 341 ++++++++++++
tcg/s390x/tcg-target.c.inc | 6 +-
tests/tcg/s390x/Makefile.target | 4 +
tests/tcg/s390x/chacha-vx.S | 914 ++++++++++++++++++++++++++++++++
4 files changed, 1262 insertions(+), 3 deletions(-)
create mode 100644 tests/tcg/s390x/chacha.c
create mode 100644 tests/tcg/s390x/chacha-vx.S
--
2.34.1
next reply other threads:[~2024-01-17 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 21:36 Richard Henderson [this message]
2024-01-17 21:36 ` [PATCH 1/2] tcg/s390x: Fix encoding of VRIc, VRSa, VRSc insns Richard Henderson
2024-01-18 6:50 ` Thomas Huth
2024-01-18 7:04 ` Richard Henderson
2024-01-19 21:54 ` Philippe Mathieu-Daudé
2024-01-17 21:36 ` [PATCH 2/2] tests/tcg/s390x: Import linux tools/testing/crypto/chacha20-s390 Richard Henderson
2024-01-17 22:45 ` Richard Henderson
2024-01-18 7:17 ` Thomas Huth
2024-01-18 6:07 ` [PATCH 0/2] tcg/s390x: Fix chacha20-s390 Michael Tokarev
2024-01-18 7:03 ` Richard Henderson
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=20240117213646.159697-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=david@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=philmd@linaro.org \
--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).