From: Al Viro <viro@ZenIV.linux.org.uk>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>,
Dave Jones <davej@redhat.com>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch: avr32: add dummy syscalls
Date: Mon, 4 Feb 2013 03:02:21 +0000 [thread overview]
Message-ID: <20130204030221.GY4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130204013111.GX4503@ZenIV.linux.org.uk>
On Mon, Feb 04, 2013 at 01:31:11AM +0000, Al Viro wrote:
> Unless I'm misreading ocavr32.pdf, that should be (R12, R10:R11, R9, R8) and
> (R12, R10:R11, R9:R8, stack) resp., so fadvise64 doesn't need a wrapper, but
> fadvise64_64 does. And something like (s32, s32, s64, s64) would turn into
> (R12, R11, R9:R8, stack, stack); AFAICS, we don't have anything that ugly...
Oh, yes, we do - fallocate(2). int fd, int mode, loff_t offset, loff_t len.
On something like mips or sparc32 it packs nicely; on avr32 it doesn't.
Could you confirm that I haven't misparsed the ABI?
> Automating *that* is going to be interesting... I've not given up, but it's
> not going to be fun ;-/
next prev parent reply other threads:[~2013-02-04 3:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 12:50 [PATCH] arch: avr32: add dummy syscalls Matthias Brugger
2013-01-27 19:57 ` Hans-Christian Egtvedt
2013-01-27 20:30 ` Al Viro
2013-01-27 20:39 ` Hans-Christian Egtvedt
2013-02-04 0:10 ` Al Viro
2013-02-04 0:30 ` Al Viro
2013-02-04 1:31 ` Al Viro
2013-02-04 3:02 ` Al Viro [this message]
2013-02-04 4:52 ` Håvard Skinnemoen
2013-02-04 5:05 ` Al Viro
2013-02-04 5:35 ` Håvard Skinnemoen
2013-02-04 15:39 ` Al Viro
2013-02-04 16:34 ` Håvard Skinnemoen
2013-02-04 22:53 ` Al Viro
2013-02-05 8:06 ` Hans-Christian Egtvedt
2013-02-04 3:21 ` H. Peter Anvin
2013-01-28 2:45 ` Håvard Skinnemoen
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=20130204030221.GY4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=will.deacon@arm.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 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.