From: "H. Peter Anvin" <hpa@zytor.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Eric Paris <eparis@redhat.com>,
linux-arch@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: sys_fanotify_mark (again)
Date: Sun, 22 Nov 2009 19:05:00 -0800 [thread overview]
Message-ID: <4B09FBDC.7010106@zytor.com> (raw)
In-Reply-To: <20091122090519.GA3974@osiris.boeblingen.de.ibm.com>
On 11/22/2009 01:05 AM, Heiko Carstens wrote:
>
> Alternatively you could also fix the syscall wrapper stuff to automatically
> do the right thing for long long parameters. But I wouldn't how... except
> with hpa's proposed automatic syscall wrapper creation engine :)
>
I really need to get off my arse and productize that, don't I...
It would help to have some examples of non-x86 ABI rules to help feed it.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2009-11-23 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 9:05 sys_fanotify_mark (again) Heiko Carstens
2009-11-23 3:05 ` H. Peter Anvin [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=4B09FBDC.7010106@zytor.com \
--to=hpa@zytor.com \
--cc=eparis@redhat.com \
--cc=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=lizf@cn.fujitsu.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).