Messages in this thread | | | Date | Mon, 15 Mar 2010 13:41:54 -0700 | From | "H. Peter Anvin" <> | Subject | Re: 64-syscall args on 32-bit vs syscall() |
| |
On 03/15/2010 01:35 PM, Benjamin Herrenschmidt wrote: > On Mon, 2010-03-15 at 12:41 -0700, H. Peter Anvin wrote: >> I don't see why syscall() can't change the type for its first argument >> -- it seems to be exactly what symbol versioning is for. >> >> Doesn't change the fact that it is fundamentally broken, of course. > > No need to change the type of the first arg and go for symbol > versionning if you do something like I proposed earlier, there will be > no conflict between syscall() and __syscall() and both variants can > exist. >
Basically symbol versioning done "by hand", actually using symbol versioning is better, IMNSHO.
-hpa
| |