linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: akpm@osdl.org, linux-arch@vger.kernel.org, sam@ravnborg.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Andi Kleen <andi@firstfloor.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Complain about missing system calls.
Date: Fri, 9 Mar 2007 20:13:08 +0000	[thread overview]
Message-ID: <20070309201308.GB8444@flint.arm.linux.org.uk> (raw)
In-Reply-To: <45F1B818.4090007@zytor.com>

On Fri, Mar 09, 2007 at 11:40:08AM -0800, H. Peter Anvin wrote:
> Jan-Benedict Glaw wrote:
> >
> >Not everybody has a simple indexed list of pointers :)  For example,
> >for vax-linux, we use a struct per syscall with the expected number of
> >on-stack longwords for the call.
> >
> >So if something "new" is coming up, please keep in mind that it should
> >be flexible enough to represent that. :)
> >
> 
> I discussed with Al Viro a while ago about using something like the 
> SYSCALLS.def file from klibc as the source format for the system calls. 
>  That would deal very flexibly with almost all kinds of stub generation.

Hopefully with this idea in place, we can spot new syscalls before
the final release of the kernel (maybe kautobuild can help there)
and fix any silly system call argument ordering which requires
different architectures to have different syscall prototypes (eg,
sys_arm_fadvise64_64 vs sys_fadvise64_64, sys_arm_sync_file_range vs
sys_sync_file_range).

Otherwise the SYSCALLS.def file will probably end up being full of
ifdefs.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2007-03-09 20:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 23:01 [PATCH] Complain about missing system calls David Woodhouse
2007-03-09  0:14 ` David Miller
2007-03-09  0:18   ` David Woodhouse
2007-03-20 12:12   ` Sam Ravnborg
2007-03-09  3:31 ` Anton Blanchard
2007-03-09  8:43 ` Russell King
2007-03-09 16:11 ` Andi Kleen
2007-03-09 16:38   ` Jan-Benedict Glaw
2007-03-09 19:00     ` Andi Kleen
2007-03-09 19:35       ` Jan-Benedict Glaw
2007-03-10  9:58       ` Martin Schwidefsky
2007-03-09 19:40     ` H. Peter Anvin
2007-03-09 20:13       ` Russell King [this message]
2007-03-09 20:52         ` H. Peter Anvin
2007-03-09 16:47   ` Benjamin Herrenschmidt
2007-03-09 18:54     ` Andi Kleen
2007-03-10  9:51       ` Martin Schwidefsky
2007-03-09 17:20   ` David Woodhouse
2007-03-19 23:42 ` Andrew Morton
2007-03-20  7:43   ` David Woodhouse
2007-03-20 10:56     ` Russell King
2007-03-20 10:51   ` David Howells
2007-03-21 11:25   ` David Woodhouse

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=20070309201308.GB8444@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=andi@firstfloor.org \
    --cc=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sam@ravnborg.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).