On Thu, Jan 14, 2010 at 05:59:39PM +1100, Benjamin Herrenschmidt wrote:
Oh I definitely agree that a direct syscall is better, and I wonder in fact if I should add new syscalls in addition to socketcall for powerpc, for glibc to do a slow migration :-) I was just wondering about the inconsistency for archs like us who have socketcall today, to also have to define the syscall ...
On ARM, we used to use socketcall exclusively. We've since added all the direct socket and IPC calls to our syscall table as part of the big EABI shakeup. They certainly get used on EABI, whereas OABI has a choice. They were made available in two stages - first the numbers were reserved and the calls were added to the call table. A few years later, we exposed the syscall numbers in unistd.h. It's now been almost 4 years since this was done, and there have been no bug reports. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
