about summary refs log tree commit diff
path: root/gmon
diff options
context:
space:
mode:
authorLukasz Majewski <lukma@denx.de>2020-04-22 10:54:01 +0200
committerLukasz Majewski <lukma@denx.de>2020-05-20 01:09:09 +0200
commit5613afe9e3dff54b10e4850804cd574e8c420e3d (patch)
tree384d23883b7a4bf99457c0e73b78f96a1bb1ff90 /gmon
parent10ae49d2ce4576d8bb8f01d1fc1cbdf550ad4cbd (diff)
downloadglibc-5613afe9e3dff54b10e4850804cd574e8c420e3d.tar.gz
glibc-5613afe9e3dff54b10e4850804cd574e8c420e3d.tar.xz
glibc-5613afe9e3dff54b10e4850804cd574e8c420e3d.zip
y2038: linux: Provide __ntp_gettime64 implementation
This patch provides new __ntp_gettime64 explicit 64 bit function for getting
time parameters via NTP interface.

Internally, the __clock_adjtime64 syscall is used instead of __adjtimex. This
patch is necessary for having architectures with __WORDSIZE == 32 Y2038 safe.

Moreover, a 32 bit version - __ntp_gettime has been refactored to internally
use __ntp_gettime64.

The __ntp_gettime 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_gettime64 and __ntp_gettime.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
Diffstat (limited to 'gmon')
0 files changed, 0 insertions, 0 deletions