Re: [PATCH 6/7] remove all remaining _syscallX macros

Andi Kleen
2006-08-28T08:28:30Z

On Monday 28 August 2006 10:19, David Miller wrote:

> I see it as duplication because the person who writes the
> kernel is the one who ends up writing the libc syscall
> bits or explains to the libc person for that arch how
> things work.

And the way to explain it is to write the reference code.

> And once one libc implmenetation of this
> exists, it can be used as a reference for other libc
> variants.

At least on x86-64 various glibc versions had quite buggy
syscall()s, that is why I never trusted it very much.

> Finally, once it's done, it's done, and that's it.

Except if you still have to deal with old user land.

-Andi