On Sun, Dec 24, 2017 at 10:25:15PM +0100, Kamil Rytarowski wrote: > It is a special syscall that returns two integers from one function > call. Fanciness is not compatible with regular C syntax and it demands > per-cpu assembly wrappers and rump-kernel workarounds. It's not easily > usable with syscall(2).
So far I see no good reason for this move. I consider the very existance of syscall(2) a bug, so any justification based on "it can't be used with it" is hallow. Joerg
