From: Jann Horn <jann@thejh.net>
To: Kees Cook <keescook@chromium.org>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
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: [PATCH v2 2/2] syscall.2: add x32 ABI
Date: Tue, 24 Mar 2015 19:40:43 +0100 [thread overview]
Message-ID: <20150324184043.GC5677@pc.thejh.net> (raw)
In-Reply-To: <20150316233457.GA9227@pc.thejh.net>
[added H. Peter Anvin to CC for this patch because he
seems to have contributed large parts of the X32 code]
---
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
next prev parent reply other threads:[~2015-03-24 18:40 UTC|newest]
Thread overview: 14+ 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
[not found] ` <20150316180154.GA10663-J1fxOzX/cBvk1uMJSBkQmQ@public.gmane.org>
2015-03-16 22:25 ` Kees Cook
2015-03-16 22:25 ` Kees Cook
2015-03-16 23:34 ` Jann Horn
2015-03-22 15:58 ` Michael Kerrisk (man-pages)
[not found] ` <20150316233457.GA9227-J1fxOzX/cBvk1uMJSBkQmQ@public.gmane.org>
2015-03-17 17:23 ` Kees Cook
2015-03-17 17:23 ` Kees Cook
2015-03-24 18:38 ` [PATCH v2 1/2] seccomp.2: Explain blacklisting problems, " Jann Horn
2015-03-24 18:38 ` Jann Horn
[not found] ` <20150324183833.GB5677-J1fxOzX/cBvk1uMJSBkQmQ@public.gmane.org>
2015-03-29 16:01 ` Michael Kerrisk (man-pages)
2015-03-29 16:01 ` Michael Kerrisk (man-pages)
2015-03-24 18:40 ` Jann Horn [this message]
[not found] ` <20150324184043.GC5677-J1fxOzX/cBvk1uMJSBkQmQ@public.gmane.org>
2015-04-21 14:01 ` [PATCH v2 2/2] syscall.2: add x32 ABI Michael Kerrisk (man-pages)
2015-04-21 14:01 ` Michael Kerrisk (man-pages)
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=20150324184043.GC5677@pc.thejh.net \
--to=jann@thejh.net \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mtk.manpages@gmail.com \
--cc=wad@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.