From: Edgar Toernig <froese@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Russell King <rmk@arm.linux.org.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Doug Ledford <dledford@redhat.com>, Keith Owens <kaos@ocs.com.au>,
Benjamin LaHaise <bcrl@redhat.com>
Subject: Re: [patch] Assigning syscall numbers for testing
Date: Tue, 25 Dec 2001 00:28:13 +0100 [thread overview]
Message-ID: <3C27BA0D.58F0A02C@gmx.de> (raw)
In-Reply-To: <3C2770FE.80403@redhat.com> <E16IaPj-0004u4-00@the-village.bc.nu> <20011224193124.F2110@flint.arm.linux.org.uk>
Russell King wrote:
>
> On Mon, Dec 24, 2001 at 07:05:31PM +0000, Alan Cox wrote:
> > > it. However, I think it needs to be allocated *regardless* of whether Linus
> > > takes the patch into his kernel. Even if the patch is simply used outside
> > > Linus's kernel, it still needs the allocation to truly be safe.
> >
> > Negative numbers are safe until Linus has 2^31 syscalls, at which point
> > quite frankly we would have a few other problems including the fact that
> > the syscall table won't fit in kernel mapped memory.
>
> Please leave the allocation of the exact number space to the port
> maintainers discression.
Why not assign 1 syscall that gets the name of an experimental syscall
as its first argument and does the demultiplexing?
Ciao, ET.
next prev parent reply other threads:[~2001-12-24 23:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 11:28 [patch] Assigning syscall numbers for testing Keith Owens
2001-12-22 14:12 ` Alan Cox
2001-12-22 14:32 ` Keith Owens
2001-12-22 19:01 ` Benjamin LaHaise
2001-12-22 23:18 ` Keith Owens
2001-12-22 23:25 ` Benjamin LaHaise
2001-12-23 0:02 ` Keith Owens
2001-12-23 4:04 ` Chris Vandomelen
2001-12-23 5:10 ` Keith Owens
2001-12-23 17:06 ` Benjamin LaHaise
2001-12-23 19:15 ` Davide Libenzi
2001-12-24 1:01 ` Keith Owens
2001-12-24 16:52 ` Doug Ledford
2001-12-24 17:11 ` Alan Cox
2001-12-24 17:06 ` Doug Ledford
2001-12-24 17:34 ` David Lang
2001-12-24 18:13 ` Doug Ledford
2001-12-24 17:54 ` David Lang
2001-12-24 18:23 ` Doug Ledford
2001-12-26 16:22 ` Riley Williams
2001-12-25 2:18 ` Keith Owens
2001-12-25 10:00 ` Russell King
2001-12-24 18:23 ` Alan Cox
2001-12-24 18:16 ` Doug Ledford
2001-12-24 19:05 ` Alan Cox
2001-12-24 19:31 ` Russell King
2001-12-24 20:46 ` Alan Cox
2001-12-24 23:28 ` Edgar Toernig [this message]
2001-12-24 23:43 ` Andreas Steinmetz
2001-12-22 20:51 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2001-12-22 11:35 Keith Owens
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=3C27BA0D.58F0A02C@gmx.de \
--to=froese@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=dledford@redhat.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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