From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: laurent@vivier.eu, iii@linux.ibm.com
Subject: Re: [PATCH 00/14] linux-user/sparc: Handle missing traps
Date: Sun, 5 Feb 2023 23:24:20 +0000 [thread overview]
Message-ID: <11a30f56-b1dc-ea1c-755c-d0c54d50c145@ilande.co.uk> (raw)
In-Reply-To: <20230202005204.2055899-1-richard.henderson@linaro.org>
On 02/02/2023 00:51, Richard Henderson wrote:
> Lots of missing trap code for cpu_loop().
>
> r~
>
> Richard Henderson (14):
> linux-user/sparc: Raise SIGILL for all unhandled software traps
> linux-user/sparc: Tidy syscall trap
> linux-user/sparc: Use TT_TRAP for flush windows
> linux-user/sparc: Tidy window spill/fill traps
> linux-user/sparc: Fix sparc64_{get,set}_context traps
> linux-user/sparc: Handle software breakpoint trap
> linux-user/sparc: Handle division by zero traps
> linux-user/sparc: Handle getcc, setcc, getpsr traps
> linux-user/sparc: Handle priviledged opcode trap
> linux-user/sparc: Handle privilidged action trap
Minor spelling nit: s/priviledged/privileged/
> linux-user/sparc: Handle coprocessor disabled trap
> linux-user/sparc: Handle unimplemented flush trap
> linux-user/sparc: Handle floating-point exceptions
> linux-user/sparc: Handle tag overflow traps
>
> linux-user/sparc/target_signal.h | 2 +-
> linux-user/syscall_defs.h | 5 +
> target/sparc/cpu.h | 3 +-
> linux-user/sparc/cpu_loop.c | 170 +++++++++++++++++++++++++------
> linux-user/sparc/signal.c | 36 +++----
> 5 files changed, 167 insertions(+), 49 deletions(-)
Alas I'm not overly familiar with the Linux syscall implementation on SPARC (all I
can really do is run a chroot debian ports install for testing), however if all your
local tests pass then I'm happy for this to go via the tcg or linux-user trees.
ATB,
Mark.
prev parent reply other threads:[~2023-02-05 23:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 0:51 [PATCH 00/14] linux-user/sparc: Handle missing traps Richard Henderson
2023-02-02 0:51 ` [PATCH 01/14] linux-user/sparc: Raise SIGILL for all unhandled software traps Richard Henderson
2023-02-02 11:56 ` Ilya Leoshkevich
2023-02-02 0:51 ` [PATCH 02/14] linux-user/sparc: Tidy syscall trap Richard Henderson
2023-02-02 1:15 ` Richard Henderson
2023-02-02 0:51 ` [PATCH 03/14] linux-user/sparc: Use TT_TRAP for flush windows Richard Henderson
2023-02-02 0:51 ` [PATCH 04/14] linux-user/sparc: Tidy window spill/fill traps Richard Henderson
2023-02-02 0:51 ` [PATCH 05/14] linux-user/sparc: Fix sparc64_{get,set}_context traps Richard Henderson
2023-02-02 0:51 ` [PATCH 06/14] linux-user/sparc: Handle software breakpoint trap Richard Henderson
2023-02-02 0:51 ` [PATCH 07/14] linux-user/sparc: Handle division by zero traps Richard Henderson
2023-02-02 0:51 ` [PATCH 08/14] linux-user/sparc: Handle getcc, setcc, getpsr traps Richard Henderson
2023-02-02 0:51 ` [PATCH 09/14] linux-user/sparc: Handle priviledged opcode trap Richard Henderson
2023-02-02 0:52 ` [PATCH 10/14] linux-user/sparc: Handle privilidged action trap Richard Henderson
2023-02-02 0:52 ` [PATCH 11/14] linux-user/sparc: Handle coprocessor disabled trap Richard Henderson
2023-02-02 0:52 ` [PATCH 12/14] linux-user/sparc: Handle unimplemented flush trap Richard Henderson
2023-02-02 0:52 ` [PATCH 13/14] linux-user/sparc: Handle floating-point exceptions Richard Henderson
2023-02-02 0:52 ` [PATCH 14/14] linux-user/sparc: Handle tag overflow traps Richard Henderson
2023-02-05 23:24 ` Mark Cave-Ayland [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=11a30f56-b1dc-ea1c-755c-d0c54d50c145@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@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 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).