diff options
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2021-07-12 18:50:22 -0300 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2021-10-04 10:51:55 -0300 |
| commit | 958309cba24caf58ea5e118b20eccadbb3638f2d (patch) | |
| tree | a7ca9e0ba9b75133e075760cd629b0db7bfdc676 /elf | |
| parent | 3692c0df7f066d01863fc05a5f7cedd2628961e7 (diff) | |
| download | glibc-958309cba24caf58ea5e118b20eccadbb3638f2d.tar.gz glibc-958309cba24caf58ea5e118b20eccadbb3638f2d.tar.xz glibc-958309cba24caf58ea5e118b20eccadbb3638f2d.zip | |
time: Ignore interval nanoseconds on tst-itimer
Running the test on a 4.4 kernel within KVM, the precision used on ITIMER_VIRTUAL and ITIMER_PROF seems to different than the one used for ITIMER_REAL (it seems the same used for CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE). I did not see it on other kernels, for instance 5.11 and 4.15. To avoid trying to guess the resolution used, do not check the nanosecond internal values for the specific timers. Checked on i686-linux-gnu with a 4.4 kernel.
Diffstat (limited to 'elf')
0 files changed, 0 insertions, 0 deletions