[haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: "Rene Gollent" <anevilyak@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 22 Mar 2008 14:46:30 -0500
> Syscalls are only the functions declared in
> headers/private/kernel/syscalls.h. The build system automatically generates
> the userland-side stubs calling the kernel and the kernel-side jump table
> referencing the respective _user_*() functions. Any other function you find
> in userland must have an implementation somewhere.
>
> It is also worth mentioning that a good deal of libroot code is recompiled
> for the kernel (cf. src/system/kernel/lib). Therefore you'll often find some
> libroot function calling a _kern_*() syscall and a normal function with just
> that signature implemented in the kernel. Other functions, like
> real_time_clock_usecs(), find_thread(), etc. are simply implemented
> separately for libroot and for the kernel.
Understood, much thanks for the clarification :)
Regards,
Rene
- References:
- [haiku-development] 64-bit syscalls in real_time_clock.c
- From: Rene Gollent
- [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: Ingo Weinhold
- [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: Rene Gollent
- [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: Ingo Weinhold
Other related posts:
- » [haiku-development] 64-bit syscalls in real_time_clock.c
- » [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- » [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- » [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- » [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- [haiku-development] 64-bit syscalls in real_time_clock.c
- From: Rene Gollent
- [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: Ingo Weinhold
- [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: Rene Gollent
- [haiku-development] Re: 64-bit syscalls in real_time_clock.c
- From: Ingo Weinhold