From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, laurent@vivier.eu
Subject: [PATCH v5 06/24] linux-user/hppa: Use the proper si_code for PRIV_OPR, PRIV_REG, OVERFLOW
Date: Fri, 7 Jan 2022 13:32:25 -0800 [thread overview]
Message-ID: <20220107213243.212806-7-richard.henderson@linaro.org> (raw)
In-Reply-To: <20220107213243.212806-1-richard.henderson@linaro.org>
These si_codes have been properly set by the kernel since the beginning.
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
---
linux-user/hppa/cpu_loop.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/linux-user/hppa/cpu_loop.c b/linux-user/hppa/cpu_loop.c
index 4740da1b7a..a65e1571a0 100644
--- a/linux-user/hppa/cpu_loop.c
+++ b/linux-user/hppa/cpu_loop.c
@@ -144,11 +144,17 @@ void cpu_loop(CPUHPPAState *env)
env->iaoq_b = env->gr[31] + 4;
break;
case EXCP_ILL:
- case EXCP_PRIV_OPR:
- case EXCP_PRIV_REG:
force_sig_fault(TARGET_SIGILL, TARGET_ILL_ILLOPN, env->iaoq_f);
break;
+ case EXCP_PRIV_OPR:
+ force_sig_fault(TARGET_SIGILL, TARGET_ILL_PRVOPC, env->iaoq_f);
+ break;
+ case EXCP_PRIV_REG:
+ force_sig_fault(TARGET_SIGILL, TARGET_ILL_PRVREG, env->iaoq_f);
+ break;
case EXCP_OVERFLOW:
+ force_sig_fault(TARGET_SIGFPE, TARGET_FPE_INTOVF, env->iaoq_f);
+ break;
case EXCP_COND:
case EXCP_ASSIST:
force_sig_fault(TARGET_SIGFPE, 0, env->iaoq_f);
--
2.25.1
next prev parent reply other threads:[~2022-01-07 21:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 21:32 [PATCH v5 00/24] linux-user: Clean up siginfo_t handling Richard Henderson
2022-01-07 21:32 ` [PATCH v5 01/24] linux-user/alpha: Set TRAP_UNK for bugchk and unknown gentrap Richard Henderson
2022-01-07 21:32 ` [PATCH v5 02/24] linux-user/alpha: Set FPE_FLTUNK for gentrap ROPRAND Richard Henderson
2022-01-07 21:32 ` [PATCH v5 03/24] linux-user/alpha: Use force_sig_fault Richard Henderson
2022-01-07 21:32 ` [PATCH v5 04/24] linux-user/cris: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 05/24] linux-user/hppa: " Richard Henderson
2022-01-07 21:32 ` Richard Henderson [this message]
2022-01-07 21:32 ` [PATCH v5 07/24] linux-user: Remove TARGET_NSIGFPE Richard Henderson
2022-01-07 21:32 ` [PATCH v5 08/24] linux-user/hppa: Set FPE_CONDTRAP for COND Richard Henderson
2022-01-07 21:32 ` [PATCH v5 09/24] linux-user/i386: Split out maybe_handle_vm86_trap Richard Henderson
2022-01-07 21:32 ` [PATCH v5 10/24] linux-user/i386: Use force_sig, force_sig_fault Richard Henderson
2022-01-07 21:32 ` [PATCH v5 11/24] linux-user/m68k: Use force_sig_fault Richard Henderson
2022-01-07 21:32 ` [PATCH v5 12/24] linux-user/microblaze: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 13/24] linux-user/microblaze: Fix SIGFPE si_codes Richard Henderson
2022-01-07 21:32 ` [PATCH v5 14/24] linux-user/mips: Improve do_break Richard Henderson
2022-01-07 21:32 ` [PATCH v5 15/24] linux-user/mips: Use force_sig_fault Richard Henderson
2022-01-07 21:32 ` [PATCH v5 16/24] target/mips: Extract break code into env->error_code Richard Henderson
2022-01-07 21:32 ` [PATCH v5 17/24] target/mips: Extract trap " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 18/24] linux-user/openrisc: Use force_sig_fault Richard Henderson
2022-01-07 21:32 ` [PATCH v5 19/24] linux-user/ppc: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 20/24] linux-user/riscv: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 21/24] linux-user/s390x: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 22/24] linux-user/sh4: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 23/24] linux-user/sparc: " Richard Henderson
2022-01-07 21:32 ` [PATCH v5 24/24] linux-user/xtensa: " Richard Henderson
2022-01-08 17:25 ` [PATCH v5 00/24] linux-user: Clean up siginfo_t handling Laurent Vivier
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=20220107213243.212806-7-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.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).