qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: chengang@emindsoft.com.cn, rth@twiddle.net,
	peter.maydell@linaro.org, cmetcalf@ezchip.com
Cc: walt@tilera.com, riku.voipio@iki.fi, qemu-devel@nongnu.org,
	Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame
Date: Tue, 29 Mar 2016 16:17:15 +0200	[thread overview]
Message-ID: <56FA8E6B.7020507@vivier.eu> (raw)
In-Reply-To: <1459259629-5312-1-git-send-email-chengang@emindsoft.com.cn>



Le 29/03/2016 15:53, chengang@emindsoft.com.cn a écrit :
> From: Chen Gang <chengang@emindsoft.com.cn>
> 
> Original implementation uses do_rt_sigreturn directly in host space,
> when a guest program is in unwind procedure in guest space, it will get
> an incorrect restore address, then causes unwind failure.
> 
> Also cleanup the original incorrect indentation.
> 
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>

Reviewed-by: Laurent Vivier <laurent@vivier.eu>

> ---
>  linux-user/signal.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/linux-user/signal.c b/linux-user/signal.c
> index 96e86c0..e487f9e 100644
> --- a/linux-user/signal.c
> +++ b/linux-user/signal.c
> @@ -5559,8 +5559,13 @@ struct target_rt_sigframe {
>      unsigned char save_area[16]; /* caller save area */
>      struct target_siginfo info;
>      struct target_ucontext uc;
> +    abi_ulong retcode[2];
>  };
>  
> +#define INSN_MOVELI_R10_139  0x00045fe551483000ULL /* { moveli r10, 139 } */
> +#define INSN_SWINT1          0x286b180051485000ULL /* { swint1 } */
> +
> +
>  static void setup_sigcontext(struct target_sigcontext *sc,
>                               CPUArchState *env, int signo)
>  {
> @@ -5636,9 +5641,12 @@ static void setup_rt_frame(int sig, struct target_sigaction *ka,
>      __put_user(target_sigaltstack_used.ss_size, &frame->uc.tuc_stack.ss_size);
>      setup_sigcontext(&frame->uc.tuc_mcontext, env, info->si_signo);
>  
> -    restorer = (unsigned long) do_rt_sigreturn;
>      if (ka->sa_flags & TARGET_SA_RESTORER) {
> -            restorer = (unsigned long) ka->sa_restorer;
> +        restorer = (unsigned long) ka->sa_restorer;
> +    } else {
> +        __put_user(INSN_MOVELI_R10_139, &frame->retcode[0]);
> +        __put_user(INSN_SWINT1, &frame->retcode[1]);
> +        restorer = frame_addr + offsetof(struct target_rt_sigframe, retcode);
>      }
>      env->pc = (unsigned long) ka->_sa_handler;
>      env->regs[TILEGX_R_SP] = (unsigned long) frame;
> 

      reply	other threads:[~2016-03-29 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 13:53 [Qemu-devel] [PATCH v2] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame chengang
2016-03-29 14:17 ` Laurent Vivier [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=56FA8E6B.7020507@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=chengang@emindsoft.com.cn \
    --cc=cmetcalf@ezchip.com \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=rth@twiddle.net \
    --cc=walt@tilera.com \
    /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).