From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM tracehook support
Date: Tue, 21 Feb 2012 17:30:37 +0000 [thread overview]
Message-ID: <20120221173037.GB1774@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120221172408.GJ23133@mudshark.cambridge.arm.com>
On Tue, Feb 21, 2012 at 05:24:09PM +0000, Will Deacon wrote:
> Ok, if the low-level code doesn't need to interpret arguments then that
> should be fine. sys_arm_fadvise64_64 would be the tricky case, but the
> argument ordering seems to have been chosen explicitly to place the 64-bit
> offsets naturally on even registers, fitting it neatly into 6 registers.
That was done because the standard argument order was impossible to pass
in the available register set with EABI. It would have meant having to
move the syscall number into r8 or higher, which would've been rather
unfriendly to Thumb code.
next prev parent reply other threads:[~2012-02-21 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 15:37 ARM tracehook support Wade Farnsworth
2012-02-20 15:47 ` Will Deacon
2012-02-20 18:08 ` Wade Farnsworth
2012-02-21 17:06 ` Wade Farnsworth
2012-02-21 17:24 ` Will Deacon
2012-02-21 17:30 ` Russell King - ARM Linux [this message]
2012-02-21 17:27 ` Russell King - ARM Linux
2012-02-21 18:08 ` Wade Farnsworth
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=20120221173037.GB1774@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).