[ppc] Disparity between sys_clock_getres and vdso implementation
sripathik at in.ibm.com
Mon Jan 28 01:02:59 EST 2008
On PPC, I see a disparity between clock_getres implementations in the
vdso and syscall. I am using a IBM Openpower hardware and 2.6.24 kernel
clock_getres call for CLOCK_REALTIME returns 1 millisecond. However,
when I edit arch/powerpc/kernel/vdso*/gettimeofday.S to force it to use
sys_clock_getres, I get 1 nanosecond resolution. The code in vdso seems
to be returning some pre-defined (incorrect) variables.
Could you please let me know the reason for this? Is it something that
should be fixed in vdso?
More information about the Linuxppc-dev