From: Alistair Francis <alistair23@gmail.com>
To: "Amanieu d'Antras" <amanieu@gmail.com>
Cc: Riku Voipio <riku.voipio@iki.fi>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] linux-user/riscv: Fix target_ucontext and target_sigcontext
Date: Mon, 27 Apr 2020 13:23:18 -0700 [thread overview]
Message-ID: <CAKmqyKOnG6Q2g0KGcPRO51UKuDiCaXu_Z3_Une2SM24obrnEew@mail.gmail.com> (raw)
In-Reply-To: <20200427201120.1500504-1-amanieu@gmail.com>
On Mon, Apr 27, 2020 at 1:11 PM Amanieu d'Antras <amanieu@gmail.com> wrote:
>
> These now match the field layout used by the kernel.
>
> Signed-off-by: Amanieu d'Antras <amanieu@gmail.com>
Thanks for the patch!
Unfortunately this fixed has already been applied to the RISC-V tree
(https://github.com/alistair23/qemu/tree/riscv-to-apply) and will be
merged once the 5.1 development window opens up.
Alistair
> ---
> linux-user/riscv/signal.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/linux-user/riscv/signal.c b/linux-user/riscv/signal.c
> index 83ecc6f799..2b15e32a7b 100644
> --- a/linux-user/riscv/signal.c
> +++ b/linux-user/riscv/signal.c
> @@ -32,7 +32,7 @@
> struct target_sigcontext {
> abi_long pc;
> abi_long gpr[31]; /* x0 is not present, so all offsets must be -1 */
> - uint64_t fpr[32];
> + uint64_t fpr[32] __attribute__((aligned(16)));
> uint32_t fcsr;
> }; /* cf. riscv-linux:arch/riscv/include/uapi/asm/ptrace.h */
>
> @@ -40,8 +40,9 @@ struct target_ucontext {
> unsigned long uc_flags;
> struct target_ucontext *uc_link;
> target_stack_t uc_stack;
> - struct target_sigcontext uc_mcontext;
> target_sigset_t uc_sigmask;
> + char __unused[1024 / 8 - sizeof(target_sigset_t)];
> + struct target_sigcontext uc_mcontext;
> };
>
> struct target_rt_sigframe {
> --
> 2.26.1
>
>
next prev parent reply other threads:[~2020-04-27 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 20:11 [PATCH] linux-user/riscv: Fix target_ucontext and target_sigcontext Amanieu d'Antras
2020-04-27 20:23 ` Alistair Francis [this message]
2020-04-27 21:04 ` no-reply
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=CAKmqyKOnG6Q2g0KGcPRO51UKuDiCaXu_Z3_Une2SM24obrnEew@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=amanieu@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).