linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jann Horn <jann@thejh.net>
Cc: Kees Cook <keescook@chromium.org>,
	linux-man <linux-man@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2 2/2] syscall.2: add x32 ABI
Date: Tue, 21 Apr 2015 16:01:11 +0200	[thread overview]
Message-ID: <CAKgNAkihLXniE+bgqi_xjVAqKcUr1Gkiq9hKGK7t_a3EPT_fJg@mail.gmail.com> (raw)
In-Reply-To: <20150324184043.GC5677@pc.thejh.net>

Hi Jann,

On 24 March 2015 at 19:40, Jann Horn <jann@thejh.net> wrote:
> [added H. Peter Anvin to CC for this patch because he
> seems to have contributed large parts of the X32 code]

It looks like I did not reply to this mail. But as you'll probably have seen
from the man-pages-3.83 release announcement, I did apply this patch.
Thanks!

Cheers,

Michael


>
> ---
>  man2/syscall.2 | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index ef8f3cf..1f25255 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -170,12 +170,18 @@ s390      svc 0   r1      r2      See below
>  s390x  svc 0   r1      r2      See below
>  sparc/32       t 0x10  g1      o0
>  sparc/64       t 0x6d  g1      o0
> -x86_64 syscall rax     rax
> +x86_64 syscall rax     rax     See below
> +x32    syscall rax     rax     See below
>  .TE
>  .PP
>  For s390 and s390x, NR (the system call number)
>  may be passed directly with "svc NR" if it is less than 256.
>
> +The x32 ABI uses the same instruction as the x86_64 ABI and is used on
> +the same processors. To differentiate between them, the bitmask
> +.I __X32_SYSCALL_BIT
> +is bitwise-ORed into the syscall number for syscalls under the x32 ABI.
> +
>  On a few architectures,
>  a register is used to indicate simple boolean failure of the system call:
>  ia64 uses
> @@ -210,6 +216,7 @@ s390x       r2    r3    r4    r5    r6    r7    -
>  sparc/32    o0    o1    o2    o3    o4    o5    -
>  sparc/64    o0    o1    o2    o3    o4    o5    -
>  x86_64      rdi   rsi   rdx   r10   r8    r9    -
> +x32         rdi   rsi   rdx   r10   r8    r9    -
>  .TE
>  .PP
>  The mips/o32 system call convention passes
> --
> 2.1.4



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2015-04-21 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 18:01 [PATCH] seccomp.2: Explain arch checking, value (non-)truncation, expand example Jann Horn
2015-03-16 22:25 ` Kees Cook
2015-03-16 23:34   ` Jann Horn
2015-03-17 17:23     ` Kees Cook
2015-03-22 15:58     ` Michael Kerrisk (man-pages)
2015-03-24 18:38     ` [PATCH v2 1/2] seccomp.2: Explain blacklisting problems, " Jann Horn
2015-03-29 16:01       ` Michael Kerrisk (man-pages)
2015-03-24 18:40     ` [PATCH v2 2/2] syscall.2: add x32 ABI Jann Horn
2015-04-21 14:01       ` Michael Kerrisk (man-pages) [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=CAKgNAkihLXniE+bgqi_xjVAqKcUr1Gkiq9hKGK7t_a3EPT_fJg@mail.gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jann@thejh.net \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=wad@chromium.org \
    --subject='Re: [PATCH v2 2/2] syscall.2: add x32 ABI' \
    /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

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).