From: Jonathan Albrecht <jonathan.albrecht@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: ruixin.bao@ibm.com,
Jonathan Albrecht <jonathan.albrecht@linux.vnet.ibm.com>,
iii@linux.ibm.com, david@redhat.com, cohuck@redhat.com,
richard.henderson@linaro.org, laurent@vivier.eu,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
krebbel@linux.ibm.com
Subject: [PATCH v2 0/2] linux-user/s390x: signal with SIGFPE on compare-and-trap
Date: Wed, 7 Jul 2021 09:42:29 -0400 [thread overview]
Message-ID: <20210707134231.1835-1-jonathan.albrecht@linux.vnet.ibm.com> (raw)
qemu-s390x signals with SIGILL on compare-and-trap instructions. This
breaks OpenJDK which expects SIGFPE in its implementation of implicit
exceptions.
This patch depends on [PATCH v6 0/2] target/s390x: Fix SIGILL and SIGFPE
psw.addr reporting
https://lore.kernel.org/qemu-devel/20210705210434.45824-1-iii@linux.ibm.com/
Based-on: 20210705210434.45824-1-iii@linux.ibm.com
v1 -> v2:
- Update to latest version of '... psw.addr reporting' patch
- Rebase to master and fix conflicts in tests/tcg/s390x/Makefile.target
Jonathan Albrecht (2):
linux-user/s390x: signal with SIGFPE on compare-and-trap
tests/tcg: Test that compare-and-trap raises SIGFPE
linux-user/s390x/cpu_loop.c | 19 +++---
tests/tcg/s390x/Makefile.target | 1 +
tests/tcg/s390x/trap.c | 102 ++++++++++++++++++++++++++++++++
3 files changed, 113 insertions(+), 9 deletions(-)
create mode 100644 tests/tcg/s390x/trap.c
--
2.31.1
next reply other threads:[~2021-07-07 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:42 Jonathan Albrecht [this message]
2021-07-07 13:42 ` [PATCH v2 1/2] linux-user/s390x: signal with SIGFPE on compare-and-trap Jonathan Albrecht
2021-07-08 17:08 ` Richard Henderson
2021-07-09 14:23 ` jonathan.albrecht
2021-07-09 14:37 ` Richard Henderson
2021-07-09 14:48 ` jonathan.albrecht
2021-07-07 13:42 ` [PATCH v2 2/2] tests/tcg: Test that compare-and-trap raises SIGFPE Jonathan Albrecht
2021-07-08 17:18 ` 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=20210707134231.1835-1-jonathan.albrecht@linux.vnet.ibm.com \
--to=jonathan.albrecht@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=krebbel@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=ruixin.bao@ibm.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).