blob: 08595c94bc691b098cd79d4c6d8a91c1dfa0bc91 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
The issue reported is related to the behavior of QEMU's user-mode emulation of the ppc64le architecture when handling vDSO calls to `clock_gettime()`. The problem causes time-based functions like `time.NewTicker()` and `time.Sleep()` in Go programs to malfunction, leading to sleeps or ticks that do not respect sub-second granularities. This suggests an issue with how QEMU handles these specific system calls or the virtual dynamic shared object (vDSO) mechanism.
Given the categories provided:
1. **instruction**: Refers to issues with individual machine instructions.
2. **syscall**: Relates to errors in handling system calls.
3. **runtime**: Covers other runtime-related issues not specifically tied to instructions or syscalls.
This issue is centered around how QEMU emulates `clock_gettime()` via vDSO, which is a system call mechanism. The problem arises during the execution of these syscalls within the user-mode emulation, leading to incorrect timing behavior. Therefore, this falls under **syscall** because it involves errors in handling system calls, specifically those related to timekeeping.
Answer: syscall
|