Re: 64-syscall args on 32-bit vs syscall()

[Ulrich Drepper]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/17/2010 01:56 AM, Benjamin Herrenschmidt wrote:
>>  - You keep the existing syscall() exported by glibc for binary
>> compatibility
> 
>>  - You add a new __syscall() (or whatever you want to name it) that adds
>> a dummy argument at the beginning, and whose implementation shifts
>> everything by 2 instead of 1 argument before calling into the kernel
> 
>>  - You define in unistd.h or whatever is relevant, a macro that does:
> 
>> #define syscall(__sysno, __args..) __syscall(0, _sysno, __args)
> 
>> I believe that should cover it, at least for powerpc, possibly for other
>> archs too though as I said, I may have missed something there.

How can this possibly be the case?  This will screw people who currently
work around the ppc limitations of the existing syscall.

Just leave it alone.

- -- 
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkugnV0ACgkQ2ijCOnn/RHRL4gCeIY0SLDCgLqtVvuMw+pvCzkwE
3MIAoJQRK5Mc+WtC/Wz9tPFPy4X+EALe
=lexw
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/