From: Will Deacon <will@kernel.org>
To: Dave Martin <Dave.Martin@arm.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-man@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] syscall.2: arm64: Fix syscall number register size
Date: Tue, 5 May 2020 16:54:57 +0100 [thread overview]
Message-ID: <20200505155457.GE24239@willie-the-truck> (raw)
In-Reply-To: <1588692280-15878-3-git-send-email-Dave.Martin@arm.com>
On Tue, May 05, 2020 at 04:24:40PM +0100, Dave Martin wrote:
> arm64 is currently documented as receiving the syscall number in
> x8.
>
> While this is the correct register, the syscall number is a 32-bit
> integer. Bits [63:32] are ignored by the kernel.
>
> So it is more correct to say "w8".
>
> Signed-off-by: Dave Martin <Dave.Martin@arm.com>
> ---
> man2/syscall.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index 53ab40e..d724651 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -203,7 +203,7 @@ alpha callsys v0 v0 a4 a3 1, 6
> arc trap0 r8 r0 - -
> arm/OABI swi NR - r0 - - 2
> arm/EABI swi 0x0 r7 r0 r1 -
> -arm64 svc #0 x8 x0 x1 -
> +arm64 svc #0 w8 x0 x1 -
Acked-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2020-05-05 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 15:24 [PATCH 0/2] syscall.2: Minor register name fixes for arm/arm64 Dave Martin
2020-05-05 15:24 ` [PATCH 1/2] syscall.2: arm: Use real register names for arm/OABI Dave Martin
2020-05-05 15:26 ` Russell King - ARM Linux admin
2020-05-05 15:53 ` Dave Martin
2020-05-06 10:05 ` Michael Kerrisk (man-pages)
2020-05-06 10:34 ` Dave Martin
2020-05-05 15:24 ` [PATCH 2/2] syscall.2: arm64: Fix syscall number register size Dave Martin
2020-05-05 15:54 ` Will Deacon [this message]
2020-05-05 16:06 ` Dave Martin
2020-05-06 10:16 ` Michael Kerrisk (man-pages)
2020-05-06 10:35 ` Dave Martin
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=20200505155457.GE24239@willie-the-truck \
--to=will@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-man@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mtk.manpages@gmail.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).