qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Warner Losh <imp@bsdimp.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
	Philippe Mathieu-Daude <f4bug@amsat.org>
Subject: Re: [RFC 4/4] common-user: Allow return codes to be adjusted after sytsem call
Date: Mon, 8 Nov 2021 16:10:22 +0100	[thread overview]
Message-ID: <0511aedf-1ecd-666d-034f-55d50306e115@linaro.org> (raw)
In-Reply-To: <20211108023738.42125-5-imp@bsdimp.com>

On 11/8/21 3:37 AM, Warner Losh wrote:
> All the *-users generally use the Linux style of negative return codes
> for errno. However, other systems, like FreeBSD, have a different
> convention. Allow those systems to insert code after the syscall that
> adjusts the return value of the system call to match the native linux
> format.
> 
> Signed-off-by: Warner Losh <imp@bsdimp.com>
> ---
>   common-user/host/aarch64/safe-syscall.inc.S | 1 +
>   common-user/host/arm/safe-syscall.inc.S     | 1 +
>   common-user/host/i386/safe-syscall.inc.S    | 1 +
>   common-user/host/ppc64/safe-syscall.inc.S   | 1 +
>   common-user/host/riscv/safe-syscall.inc.S   | 1 +
>   common-user/host/s390x/safe-syscall.inc.S   | 1 +
>   common-user/host/x86_64/safe-syscall.inc.S  | 1 +
>   linux-user/safe-syscall.S                   | 1 +
>   8 files changed, 8 insertions(+)
> 
> diff --git a/common-user/host/aarch64/safe-syscall.inc.S b/common-user/host/aarch64/safe-syscall.inc.S
> index bc1f5a9792..81d83e8e79 100644
> --- a/common-user/host/aarch64/safe-syscall.inc.S
> +++ b/common-user/host/aarch64/safe-syscall.inc.S
> @@ -64,6 +64,7 @@ safe_syscall_start:
>   	svc	0x0
>   safe_syscall_end:
>   	/* code path for having successfully executed the syscall */
> +	ADJUST_SYSCALL_RETCODE
>   	ret
>   
>   0:

Not sure about this, really.  Is it really that much cleaner to insert this than create 
separate 10-line files, with the adjustment included?


r~


  reply	other threads:[~2021-11-08 15:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08  2:37 [RFC 0/4] linux-user: simplify safe signal handling Warner Losh
2021-11-08  2:37 ` [RFC 1/4] linux-user: Add host_signal_set_pc to set pc in mcontext Warner Losh
2021-11-08 15:03   ` Richard Henderson
2021-11-10 15:43   ` Philippe Mathieu-Daudé
2021-11-08  2:37 ` [RFC 2/4] linux-user/signal.c: Create a common rewind_if_in_safe_syscall Warner Losh
2021-11-08 15:07   ` Richard Henderson
2021-11-08 16:39     ` Warner Losh
2021-11-10 16:20       ` Warner Losh
2021-11-10 16:31         ` Richard Henderson
2021-11-10 15:44   ` Philippe Mathieu-Daudé
2021-11-08  2:37 ` [RFC 3/4] linux-user/safe-syscall.inc.S: Move to common-user Warner Losh
2021-11-08  2:37 ` [RFC 4/4] common-user: Allow return codes to be adjusted after sytsem call Warner Losh
2021-11-08 15:10   ` Richard Henderson [this message]
2021-11-08 18:49     ` Warner Losh
2021-11-09  8:11       ` Richard Henderson
2021-11-10  2:10         ` Warner Losh

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=0511aedf-1ecd-666d-034f-55d50306e115@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=imp@bsdimp.com \
    --cc=laurent@vivier.eu \
    --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).