It doesn't make sense to me to use a specially formatted page forced
into user space to tell libraries how to do system calls. Perhaps each
executable personality in the kernel should export a special shared
library in it's own native format that contains the necessary
information. That way we don't have to worry as much about code or
values changing sizes or locations.
We would have the chicken/egg problem with how the special shared
library gets loaded in the first place. For that we either support a
legacy syscall method (i.e. int 0x80 on x86) which should only be used
by ld.so or the equivalent or magically force the library into user
space at a known address.
Ross
Linus Torvalds wrote:
>On 17 Dec 2002, Alan Cox wrote:
>
>
>>Is there any reason you can't just keep the linker out of the entire
>>mess by generating
>>
>> .byte whatever
>> .dword 0xFFFF0000
>>
>>instead of call ?
>>
>>
>
>Alan, the problem is that there _is_ no such instruction as a "call
>absolute".
>
>There is only a "call relative" or "call indirect-absolute". So you either
>have to indirect through memory or a register, or you have to fix up the
>call at link-time.
>
>Yeah, I know it sounds strange, but it makes sense. Absolute calls are
>actually very unusual, and using relative calls is _usually_ the right
>thing to do. It's only in cases like this that we really want to call a
>specific address.
>
> Linus
>
>-
>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/
>
>
-
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/
This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:17 EST