From: Eric Farman <farman@linux.ibm.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
Cornelia Huck <cohuck@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>
Cc: David Hildenbrand <david@kernel.org>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] target/s390x/tcg: Set STCK/STCKF condition code after the store
Date: Fri, 31 Jul 2026 13:56:40 -0400 [thread overview]
Message-ID: <488e5ec0-2b96-4cb7-830d-76c8e493e05b@linux.ibm.com> (raw)
In-Reply-To: <20260714203206.363028-1-iii@linux.ibm.com>
On 7/14/26 4:29 PM, Ilya Leoshkevich wrote:
> Hi,
>
> Ido reported an assertion failure after failing STCKF and provided a
> small assembly snippet that causes it.
>
> This series fixes the issue and adds a test based on that snippet.
>
> Best regards,
> Ilya
>
> Ilya Leoshkevich (2):
> target/s390x/tcg: Set STCK/STCKF condition code after the store
> tests/tcg/s390x: Test STCKF condition code on a faulting store
Thanks! Applied for 11.2
>
> target/s390x/tcg/insn-data.h.inc | 4 +--
> target/s390x/tcg/translate.c | 2 ++
> tests/tcg/s390x/Makefile.target | 1 +
> tests/tcg/s390x/stckf.c | 44 ++++++++++++++++++++++++++++++++
> 4 files changed, 49 insertions(+), 2 deletions(-)
> create mode 100644 tests/tcg/s390x/stckf.c
>
prev parent reply other threads:[~2026-07-31 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 20:29 [PATCH v2 0/2] target/s390x/tcg: Set STCK/STCKF condition code after the store Ilya Leoshkevich
2026-07-14 20:29 ` [PATCH v2 1/2] " Ilya Leoshkevich
2026-07-14 20:29 ` [PATCH v2 2/2] tests/tcg/s390x: Test STCKF condition code on a faulting store Ilya Leoshkevich
2026-07-29 16:51 ` [PATCH v2 0/2] target/s390x/tcg: Set STCK/STCKF condition code after the store Eric Farman
2026-07-31 17:56 ` Eric Farman [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=488e5ec0-2b96-4cb7-830d-76c8e493e05b@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@kernel.org \
--cc=iii@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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.