Messages in this thread | | | From | Andi Kleen <> | Subject | Re: [PATCH 6/7] remove all remaining _syscallX macros | Date | Mon, 28 Aug 2006 10:28:13 +0200 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |