qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>,
	dgibson@redhat.com, riku.voipio@iki.fi,
	richard.henderson@linaro.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: ppc64: don't use volatile register during safe_syscall
Date: Thu, 26 Jul 2018 09:48:17 +0200	[thread overview]
Message-ID: <ef4f08e5-910f-a77b-6671-996be94e3c7f@vivier.eu> (raw)
In-Reply-To: <153258768962.6738.11319866502689416568.stgit@dhcp-9-109-246-16>

Le 26/07/2018 à 08:48, Shivaprasad G Bhat a écrit :
> r11 is a volatile register on PPC as per calling conventions.
> The safe_syscall code uses it to check if the signal_pending
> is set during the safe_syscall. When a syscall is interrupted
> on return from signal handling, the r11 might be corrupted
> before we retry the syscall leading to a crash. The registers
> r0-r13 are not to be used here as they have
> volatile/designated/reserved usages. Change the code to use
> r14 which is non-volatile and is appropriate for local use in
> safe_syscall.
> 
> Signed-off-by: Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>
> ---
> Steps to reproduce:
> On PPC host, issue `qemu-ppc64le /usr/bin/cc -E -`
> Attempt Ctrl-C, the issue is reproduced.
> 
> Reference:
> https://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi-1.9.html#REG

I think these comments should be included in the commit message.
Using the example of qemu-x86_64 on ppc64 would be less ambiguous.

I've tested on ppc64:

    qemu-x86_64 /usr/bin/cc -E -

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

>  linux-user/host/ppc64/safe-syscall.inc.S |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

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

Thanks,
Laurent

  reply	other threads:[~2018-07-26  7:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  6:48 [Qemu-devel] [PATCH] linux-user: ppc64: don't use volatile register during safe_syscall Shivaprasad G Bhat
2018-07-26  7:48 ` Laurent Vivier [this message]
2018-07-26 17:15 ` Richard Henderson
2018-07-26 17:39   ` Laurent Vivier
2018-07-27  4:47     ` Richard Henderson
2018-07-27  8:01       ` Laurent Vivier
2018-07-26 17:26 ` Richard Henderson
2018-07-27  6:42   ` Shivaprasad G Bhat

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=ef4f08e5-910f-a77b-6671-996be94e3c7f@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=dgibson@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=riku.voipio@iki.fi \
    --cc=sbhat@linux.vnet.ibm.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).