Ok, next try. This time a full series that tries to kill
off __KERNEL_SYSCALLS__, _syscallX() and the global errno
for good.
Practically no testing so far, so please check if this
makes sense first before applying.
I'd especially like the arch maintainers to provide
better implementations of kernel_execve, since I had to
rely on the inline assembly provided from _syscall3 to
implement them instead of doing it the right way.
Arnd <><
Arnd Bergmann <[email protected]> wrote:
> Ok, next try. This time a full series that tries to kill
> off __KERNEL_SYSCALLS__, _syscallX() and the global errno
> for good.
Have you checked uClibc? Does that use _syscallX()?
David
On Tuesday 29 August 2006 11:12, David Howells wrote:
> > Ok, next try. This time a full series that tries to kill
> > off __KERNEL_SYSCALLS__, _syscallX() and the global errno
> > for good.
>
> Have you checked uClibc? ?Does that use _syscallX()?
uClibc has its own copy of these macros.
Arnd <><
On 8/29/06, David Howells <[email protected]> wrote:
> Arnd Bergmann <[email protected]> wrote:
>
> > Ok, next try. This time a full series that tries to kill
> > off __KERNEL_SYSCALLS__, _syscallX() and the global errno
> > for good.
>
> Have you checked uClibc? Does that use _syscallX()?
At least the latest version provides its own set of _syscallX()
macros. I removed _syscallX() from the AVR32 kernel a few weeks ago as
suggested by David Woodhouse, and uClibc doesn't seem to have a
problem with it.
Haavard