From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH 8/8] linux-user/sparc64: Implement signals
Date: Sun, 25 Apr 2021 09:08:39 -0700 [thread overview]
Message-ID: <46839d70-81a8-b95c-667e-f7f03be06e5b@linaro.org> (raw)
In-Reply-To: <20210425155749.896330-9-richard.henderson@linaro.org>
On 4/25/21 8:57 AM, Richard Henderson wrote:
> We've been using the 32-bit sparc abi for 64-bit signals.
> There's a surprising amount of difference, beginning with
> the fact that 64-bit always uses rt signal frames.
>
> Signed-off-by: Richard Henderson<richard.henderson@linaro.org>
> ---
> linux-user/sparc/target_signal.h | 2 +
> linux-user/sparc64/target_syscall.h | 14 +-
> linux-user/sparc64/signal.c | 245 +++++++++++++++++++++++++++-
> 3 files changed, 254 insertions(+), 7 deletions(-)
Ho hum. I just realized I've broken sparc32plus.
I'll have to reorg the ifdefs.
r~
prev parent reply other threads:[~2021-04-25 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 15:57 [PATCH 0/8] linux-user/sparc64: Implement signals Richard Henderson
2021-04-25 15:57 ` [PATCH 1/8] linux-user: Split out target_restore_altstack Richard Henderson
2021-04-25 15:57 ` [PATCH 2/8] linux-user: Use target_restore_altstack in all sigreturn Richard Henderson
2021-04-25 15:57 ` [PATCH 3/8] linux-user: Pass CPUArchState to do_sigaltstack Richard Henderson
2021-04-25 15:57 ` [PATCH 4/8] linux-user: Pass CPUArchState to target_restore_altstack Richard Henderson
2021-04-25 18:12 ` Warner Losh
2021-04-25 15:57 ` [PATCH 5/8] linux-user/sparc64: Move sparc64 code out of sparc32 signal.c Richard Henderson
2021-04-25 18:10 ` Warner Losh
2021-04-25 15:57 ` [PATCH 6/8] linux-user/sparc: Clean up init_thread Richard Henderson
2021-04-25 15:57 ` [PATCH 7/8] linux-user/sparc64: Include TARGET_STACK_BIAS in get_sp_from_cpustate Richard Henderson
2021-04-25 15:57 ` [PATCH 8/8] linux-user/sparc64: Implement signals Richard Henderson
2021-04-25 16:08 ` Richard Henderson [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=46839d70-81a8-b95c-667e-f7f03be06e5b@linaro.org \
--to=richard.henderson@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).