blob: b7cbf51de5f8d53b68c393bf055ad0887e865f37 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
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:
|