qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: laurent@vivier.eu, Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH v2 01/15] linux-user/sparc: Raise SIGILL for all unhandled software traps
Date: Wed, 15 Feb 2023 19:45:02 -1000	[thread overview]
Message-ID: <20230216054516.1267305-2-richard.henderson@linaro.org> (raw)
In-Reply-To: <20230216054516.1267305-1-richard.henderson@linaro.org>

The linux kernel's trap tables vector all unassigned trap
numbers to BAD_TRAP, which then raises SIGILL.

Tested-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reported-by: Ilya Leoshkevich <iii@linux.ibm.com>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
---
 linux-user/sparc/cpu_loop.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/linux-user/sparc/cpu_loop.c b/linux-user/sparc/cpu_loop.c
index 434c90a55f..c120c42278 100644
--- a/linux-user/sparc/cpu_loop.c
+++ b/linux-user/sparc/cpu_loop.c
@@ -248,6 +248,14 @@ void cpu_loop (CPUSPARCState *env)
             cpu_exec_step_atomic(cs);
             break;
         default:
+            /*
+             * Most software trap numbers vector to BAD_TRAP.
+             * Handle anything not explicitly matched above.
+             */
+            if (trapnr >= TT_TRAP && trapnr <= TT_TRAP + 0x7f) {
+                force_sig_fault(TARGET_SIGILL, ILL_ILLTRP, env->pc);
+                break;
+            }
             fprintf(stderr, "Unhandled trap: 0x%x\n", trapnr);
             cpu_dump_state(cs, stderr, 0);
             exit(EXIT_FAILURE);
-- 
2.34.1



  reply	other threads:[~2023-02-16  5:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  5:45 [PATCH v2 00/15] linux-user/sparc: Handle missing traps Richard Henderson
2023-02-16  5:45 ` Richard Henderson [this message]
2023-02-16  6:07   ` [PATCH v2 01/15] linux-user/sparc: Raise SIGILL for all unhandled software traps Richard Henderson
2023-02-16  5:45 ` [PATCH v2 02/15] linux-user/sparc: Tidy syscall trap Richard Henderson
2023-02-16  7:51   ` Philippe Mathieu-Daudé
2023-02-16  5:45 ` [PATCH v2 03/15] linux-user/sparc: Tidy syscall error return Richard Henderson
2023-02-16  5:45 ` [PATCH v2 04/15] linux-user/sparc: Use TT_TRAP for flush windows Richard Henderson
2023-02-16  7:54   ` Philippe Mathieu-Daudé
2023-02-16  5:45 ` [PATCH v2 05/15] linux-user/sparc: Tidy window spill/fill traps Richard Henderson
2023-02-16  7:55   ` Philippe Mathieu-Daudé
2023-02-16  5:45 ` [PATCH v2 06/15] linux-user/sparc: Fix sparc64_{get, set}_context traps Richard Henderson
2023-02-16  5:45 ` [PATCH v2 07/15] linux-user/sparc: Handle software breakpoint trap Richard Henderson
2023-02-16  5:45 ` [PATCH v2 08/15] linux-user/sparc: Handle division by zero traps Richard Henderson
2023-02-16  5:45 ` [PATCH v2 09/15] linux-user/sparc: Handle getcc, setcc, getpsr traps Richard Henderson
2023-02-16  5:45 ` [PATCH v2 10/15] linux-user/sparc: Handle priviledged opcode trap Richard Henderson
2023-02-16  5:45 ` [PATCH v2 11/15] linux-user/sparc: Handle privilidged action trap Richard Henderson
2023-02-16  5:45 ` [PATCH v2 12/15] linux-user/sparc: Handle coprocessor disabled trap Richard Henderson
2023-02-16  5:45 ` [PATCH v2 13/15] linux-user/sparc: Handle unimplemented flush trap Richard Henderson
2023-02-16  5:45 ` [PATCH v2 14/15] linux-user/sparc: Handle floating-point exceptions Richard Henderson
2023-02-16  5:45 ` [PATCH v2 15/15] linux-user/sparc: Handle tag overflow traps Richard Henderson
2023-03-07 15:56 ` [PATCH v2 00/15] linux-user/sparc: Handle missing traps Laurent Vivier
2023-03-07 17:07   ` Richard Henderson
2023-03-07 18:23     ` 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=20230216054516.1267305-2-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=iii@linux.ibm.com \
    --cc=laurent@vivier.eu \
    --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).