[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1860053] Re: Possible lack of precision when calling clock_gettime
[Bug 1860053] Re: Possible lack of precision when calling clock_gettime via vDSO on user mode ppc64le
Fri, 17 Jan 2020 06:46:01 -0000
** Tags added: linux-user ppc
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Possible lack of precision when calling clock_gettime via vDSO on user
Status in QEMU:
Occurs on QEMU v4.2.0 run on docker (via the qemu-user-static:v4.2.0-2
image) on an AMD64 Ubuntu 18.04.3 LTS machine provided by travis-
From golang's https://github.com/golang/go/issues/36592:
It was discovered that golang's time.NewTicker() and time.Sleep()
malfunction when a compiled application was run via QEMU's ppc64le
emulator in user mode.
The methods did not malfunction on actual PowerPC hardware or when the
same golang application was compiled for golang's arm, arm64 or 386
targets and was run via user mode QEMU on the same system.
Curiously, the methods also worked when the program was compiled under
go 1.11, but do malfunction in go 1.12 and 1.13.
It was identified the change in behaviour was most likely attributable to
golang switching to using vSDO for calling clock_gettime() on PowerPC 64
architectures in 1.12. I.E:
We therefore suspect there may be a bug in QEMU's user-mode emulation
of ppc64le as relates to vDSO calls to clock_gettime().
The nature of the malfunction of time.NewTicker() and time.Sleep() is
such that sleeps or ticks with a granularity of less than one second
do not appear to be possible (they all revert to 1 second
sleeps/ticks). Could it be that the nanoseconds field of
clock_gettime() is getting lost in the vDSO version but not in the
syscall? Or some other issue calling these methods via vDSO?
Thanks in advance.
To manage notifications about this bug go to: