open trail
As part of my quest to rewrite my ~111 syscalls I was experimenting with a vDSO, where the kernel maps a shared library into a process' address space containing functions to handle syscalls.
I basically wrote half a dynamic linker getting this to work, and the OS is currently a vegetable with the two amazing syscalls of log and getting the system uptime. Now I have to figure out how the hell I'm going to get this to work alongside mlibc.
high leaf
cool!
frigid summit
interesting
dull sigil
Cool indeed
drifting laurel
@open trail it would be interesting to hear the difficulties of integrating this with mlibc!
earnest niche
@open trail how’s the progress on the vDSO
open trail
I've been "studying" so haven't done anything in like 2 weeks
but it all works now
I was reimplementing a lot of my VFS and syscalls
to actually work as expected for a unix like
earnest niche
Nice!
frigid summit
How is this better or different than providing a standard library to link in for system calls?
Asking out of ignorance
open trail
well first of all it means I can break abi
second I plan on having various calls such as getting the system timer moved completely into userspace
earnest niche
and it means that you can have the kernel use syscall/sysenter depending on the CPU vendor
not really the main point, but cool nevertheless
frigid summit
and it means that you can have the kernel use syscall/sysenter depending on the ...
That's true
Is the intention to have it be the only interface for doing system calls?
earnest niche
Is the intention to have it be the only interface for doing system calls?
yeah
queen nymph