linux-mips
[Top] [All Lists]

Re: linux-vserver syscall ...

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: linux-vserver syscall ...
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Wed, 9 Jun 2004 16:44:22 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <20040608235400.GA31706@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20040524182915.GA27481@MAIL.13thfloor.at> <20040608235400.GA31706@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Wed, Jun 09, 2004 at 01:54:00AM +0200, Ralf Baechle wrote:
> On Mon, May 24, 2004 at 08:29:15PM +0200, Herbert Poetzl wrote:
> 
> > obviously I forgot to ask you to reserve a
> > syscall for linux-vserver, and I just discovered
> > this as the currently used number (273) was used
> > up by some other syscall (in 2.6.7-rc1) ...
> > 
> > so I'm asking you now, could you please reserve
> > a syscall for this project, so that we do not
> > need to change it on every new kernel release?
> > 
> > here is a list of currently reserved syscalls
> > (for other archs) and some links to the project
> > (in case you care)
> 
> Not really - other than the fact that I'm reluctant to reserve syscall
> numbers for something that might never make it into the kernel so
> usually i386 reserving a syscall is what convinces me ...
> 
> Due to the three support ABIs you actually get 3 syscall numbers even.
> o32 gets 277, N64 236 and N32 240.  Patch is below.

thank you very much!

best,
Herbert

>   Ralf

<Prev in Thread] Current Thread [Next in Thread>