From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Shawn Anastasio <shawn@anastas.io>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH] syscall.2: Add information for powerpc64
Date: Fri, 13 Sep 2019 11:54:45 +0200 [thread overview]
Message-ID: <c6e02a23-fdd7-1dd2-ef1c-d4f6d174c521@gmail.com> (raw)
In-Reply-To: <20190913060326.12808-1-shawn@anastas.io>
Hello Shawn,
On 9/13/19 8:03 AM, Shawn Anastasio wrote:
> Add powerpc64 to the calling convention tables.
Thanks. Patch applied.
Cheers,
Michael
> Signed-off-by: Shawn Anastasio <shawn@anastas.io>
> ---
> man2/syscall.2 | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index 33e5ea655..8db5c14e2 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -196,6 +196,7 @@ mips syscall v0 v0 v1 a3 1, 6
> nios2 trap r2 r2 - r7
> parisc ble 0x100(%sr2, %r0) r20 r28 - -
> powerpc sc r0 r3 - r0 1
> +powerpc64 sc r0 r3 - cr0.SO 1
> riscv ecall a7 a0 a1 -
> s390 svc 0 r1 r2 r3 - 3
> s390x svc 0 r1 r2 r3 - 3
> @@ -220,6 +221,11 @@ On sparc, the carry bit
> in the processor status register
> .RI ( psr )
> is used instead of a full register.
> +On powerpc64, the summary overflow bit
> +.RI ( SO )
> +in field 0 of the condition register
> +.RI ( cr0 )
> +is used.
> .IP [2]
> .I NR
> is the system call number.
> @@ -322,6 +328,7 @@ mips/n32,64 a0 a1 a2 a3 a4 a5 -
> nios2 r4 r5 r6 r7 r8 r9 -
> parisc r26 r25 r24 r23 r22 r21 -
> powerpc r3 r4 r5 r6 r7 r8 r9
> +powerpc64 r3 r4 r5 r6 r7 r8 -
> riscv a0 a1 a2 a3 a4 a5 -
> s390 r2 r3 r4 r5 r6 r7 -
> s390x r2 r3 r4 r5 r6 r7 -
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2019-09-13 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 6:03 [PATCH] syscall.2: Add information for powerpc64 Shawn Anastasio
2019-09-13 9:54 ` 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=c6e02a23-fdd7-1dd2-ef1c-d4f6d174c521@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=shawn@anastas.io \
/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).