[lkml]   [2010]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 64-syscall args on 32-bit vs syscall()
On 03/15/2010 12:00 PM, David Miller wrote:
> From: Ulrich Drepper <>
> Date: Mon, 15 Mar 2010 09:00:55 -0700
>> On 03/15/2010 08:13 AM, H. Peter Anvin wrote:
>>> One option would be to do a,
>> No need. Put it in the vdso. And name it something other than syscall.
>> The syscall() API is fixed, you cannot change it.
>> All this only if it makes sense for ALL archs. If it cannot work for
>> just one arch then it's not worth it at all.
> There are many archs that still lack VDSO.

Putting it into the vdso is also rather annoyingly heavyweight for what
is nothing other than an ordinary shared library. Just making it an
ordinary shared library seems a lot saner.

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.


 \ /
  Last update: 2010-03-15 20:49    [W:0.057 / U:2.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site