diff options
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1111')
| -rw-r--r-- | gitlab/issues_text/target_missing/host_missing/accel_missing/1111 | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1111 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1111 deleted file mode 100644 index 8548a6ee4..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/1111 +++ /dev/null @@ -1,18 +0,0 @@ -Calling FUTEX_LOCK_PI with qemu-x86_64-static caused ENOSYS error. -Description of problem: -When I executed the command "perf bench futex lock-pi" in amd64 docker image on s390x, I got the following error. -``` -perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented -perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented -perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented -perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented -``` - -I searched for this error message in the source code of perf-bench. I think that the following system call caused ENOSYS error. -` syscall(SYS_futex, uaddr, FUTEX_LOCK_PI | opflags, val, timeout, uaddr2, val3)` -Steps to reproduce: -1. Execute the command "perf bench futex lock-pi" in amd64 docker image on s390x -2. -3. -Additional information: - |