[Top] [All Lists]

Re: N32 support in 64-bit MIPS Linux

To: Kjeld Borch Egevang <>
Subject: Re: N32 support in 64-bit MIPS Linux
From: Ralf Baechle <>
Date: Thu, 15 Aug 2002 18:19:52 +0200
Cc: linux-mips mailing list <>
In-reply-to: <>; from on Thu, Aug 15, 2002 at 12:06:31PM +0200
References: <>
User-agent: Mutt/
On Thu, Aug 15, 2002 at 12:06:31PM +0200, Kjeld Borch Egevang wrote:

> I would like to hear your opinion on this.
> Currently we have the N64 interface which is the basic interface to the
> kernel. Then we have the O32 interface which is implemented as a separate
> set of syscalls in unistd.h and proper conversion in the kernel.
> Now, how can we support N32? Many syscalls will work if N32 is treated the
> same way as O32. This will of course mean, that O32 must be compiled in in
> order to support N32. But e.g. a syscall like:
> int _llseek(unsigned int fd, unsigned long offset_high, unsigned long 
> offset_low, loff_t *result, unsigned int whence);
> needs special treatment since loff_t is a long long (passed in a single
> register for N32) and there are 6 arguments (all passed in registers for
> N32, passed in registers and on the stack for O32).
> Should we simply add 235 new syscall numbers to unistd.h named 
> __NR_LinuxN32...?

o32 currently has 240 syscalls.  Of these a good number is simply
junk.  No syscall(2), oldstat(2), oldfstat(2), no experimental
UNIX Version 7 bs like mpx(2) for new ABIs; away with stupid multiplexor
calls like socketcall(2) and funny intelisms like vm86(2).  That's
the first cleanup I'm planning.

For what will be left over, N32 and N64 use the same subroutine calling
interface we'll be able to share most if not all syscalls between the two.
llseek(2) is just one example.


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