Messages in this thread | | | Date | Sun, 14 Mar 2010 22:06:46 -0700 (PDT) | Subject | Re: 64-syscall args on 32-bit vs syscall() | From | David Miller <> |
| |
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: Mon, 15 Mar 2010 15:48:13 +1100
> As it is, any 32-bit app using syscall() on any of the syscalls that > takes 64-bit arguments will be broken, unless the app itself breaks up > the argument, but the the order of the hi and lo part is different > between BE and LE architectures ;-)
I think it is even different on the same endian architectures, f.e. mips I think.
There is no way to do this without some arch specific code to handle things properly, really.
| |