diff options
author | Lukasz Majewski <lukma@denx.de> | 2020-04-22 10:49:39 +0200 |
---|---|---|
committer | Lukasz Majewski <lukma@denx.de> | 2020-05-20 01:09:16 +0200 |
commit | 4c4fc04826c2e02635c65163efb1244148735c41 (patch) | |
tree | 74405872e21b54ea0e9eb3e841844683075fcb25 /manual/threads.texi | |
parent | 5613afe9e3dff54b10e4850804cd574e8c420e3d (diff) | |
download | glibc-4c4fc04826c2e02635c65163efb1244148735c41.tar.gz glibc-4c4fc04826c2e02635c65163efb1244148735c41.tar.xz glibc-4c4fc04826c2e02635c65163efb1244148735c41.zip |
y2038: linux: Provide __ntp_gettimex64 implementation
This patch provides new __ntp_gettimex64 explicit 64 bit function for getting time parameters via NTP interface. The call to __adjtimex in __ntp_gettime64 function has been replaced with direct call to __clock_adjtime64 syscall, to simplify the code. Moreover, a 32 bit version - __ntp_gettimex has been refactored to internally use __ntp_gettimex64. The __ntp_gettimex is now supposed to be used on systems still supporting 32 bit time (__TIMESIZE != 64) - hence the necessary conversions between struct ntptimeval and 64 bit struct __ntptimeval64. Build tests: ./src/scripts/build-many-glibcs.py glibcs Run-time tests: - Run specific tests on ARM/x86 32bit systems (qemu): https://github.com/lmajewski/meta-y2038 and run tests: https://github.com/lmajewski/y2038-tests/commits/master Above tests were performed with Y2038 redirection applied as well as without to test the proper usage of both __ntp_gettimex64 and __ntp_gettimex. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'manual/threads.texi')
0 files changed, 0 insertions, 0 deletions