Re: [patch] Assigning syscall numbers for testing
Keith Owens (firstname.lastname@example.org)
Sun, 23 Dec 2001 01:32:55 +1100
On Sat, 22 Dec 2001 14:12:45 +0000 (GMT),
Alan Cox <email@example.com> wrote:
>> User space code should open /proc/dynamic_syscalls, read the lines
>> looking for their syscall name, extract the number and call the glibc
>> syscall() function using that number. Do not use the _syscalln()
>> functions, they require a constant syscall number at compile time.
>Simple brutal and to the point. Also it means a dynamic library can
>switch to real syscalls and dynamic apps will migrate fine.
>One request - can we specify a namespace of the form
>vendorid is the wrong phrase but "some sane way of knowing whose syscall
>it is" - it would be bad for andrea-aio and ben-aio to use the same names..
Did that in the comments.
* register_dynamic_syscall - assign a dynamic syscall number.
* @name: the name of the syscall, used by user space code to find the number.
* Use a unique name, if there is any possibility of conflict with
* other test syscalls then include your company or initials in the name.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/