VDSO
Hi,
I'm intending to start work on a proper VDSO implementation for MIPS that can provide user implementations of gettimeofday() and such, as well as take over from the current signal return trampoline code.
Just wondering if there's anyone else who's doing any work towards this so we can avoid duplication of effort if so?
Thanks,
Alex
Quoted 6 lines · Alex Smith
Hi,
I'm intending to start work on a proper VDSO implementation for MIPS that can provide user implementations of
gettimeofday()and such, as well as take over from the current signal return trampoline code.Just wondering if there's anyone else who's doing any work towards this so we can avoid duplication of effort if so?
I am not working on it, but have a small laundry list of what could be done:
1) Perhaps the VA of the vdso needs to be randomized.
2) Provide proper .eh_frame data for the signal return trampolines.
3) gettimeofday (as you suggest).
4) Provide optimized versions of memcpy, etc.
David Daney
Quoted 8 lines · David Daney
Quoted 6 lines · Alex Smith
Hi,
I'm intending to start work on a proper VDSO implementation for MIPS that can provide user implementations of
gettimeofday()and such, as well as take over from the current signal return trampoline code.Just wondering if there's anyone else who's doing any work towards this so we can avoid duplication of effort if so?
Quoted 7 lines
I am not working on it, but have a small laundry list of what could be done:
1) Perhaps the VA of the vdso needs to be randomized.
2) Provide proper .eh_frame data for the signal return trampolines.
3) gettimeofday (as you suggest).
Yes, I intend to do all of these.
Quoted 1 line
4) Provide optimized versions of memcpy, etc.
Is this something that belongs in a VDSO? memcpy and friends aren't syscalls, this belongs in libc IMO. ELF HWCAP flags provided by the kernel could be used by libc to decide which CPU features it can make use of to implement them.
Thanks,
Alex
Quoted 4 lines
David Daney