From: Dave Martin <Dave.Martin@arm.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-man@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] syscall.2: arm: Use real register names for arm/OABI
Date: Tue, 5 May 2020 16:53:17 +0100 [thread overview]
Message-ID: <20200505155317.GO30377@arm.com> (raw)
In-Reply-To: <20200505152658.GL1551@shell.armlinux.org.uk>
On Tue, May 05, 2020 at 04:26:58PM +0100, Russell King - ARM Linux admin wrote:
> On Tue, May 05, 2020 at 04:24:39PM +0100, Dave Martin wrote:
> > The arm OABI syscall interface is currently documented in terms of
> > register name aliases defined by the ARM Procedure Call Standard
> > (APCS). However, these don't make sense in the context of a binary
> > interface that doesn't comply (or need to comply) with APCS.
> >
> > Use the real architectural register names instead.
> >
> > The names a1-a4, v1... are just aliases for r0-r3, r4... anyway, so
> > the interface is just the same regardless of which set of names is
> > used.
> >
> > Signed-off-by: Dave Martin <Dave.Martin@arm.com>
>
> Thanks Dave,
>
> Acked-by: Russell King <rmk+kernel@armlinux.org.uk>
Thanks!
---Dave
next prev parent reply other threads:[~2020-05-05 15:53 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 [this message]
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
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=20200505155317.GO30377@arm.com \
--to=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 \
--cc=will@kernel.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).