blob: 79de191de68fa6dc92e7dd212394fb4f167be53b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
id = 1111
title = "Calling FUTEX_LOCK_PI with qemu-x86_64-static caused ENOSYS error."
state = "closed"
created_at = "2022-07-19T07:20:18.586Z"
closed_at = "2022-11-14T21:28:53.466Z"
labels = ["Closed::Fixed", "kind::Feature Request", "linux-user"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/1111"
host-os = "Ubuntu20.04"
host-arch = "s390x"
qemu-version = "qemu-x86_64 version 4.2.1 (Debian 1:4.2-3ubuntu6.23)"
guest-os = "Ubuntu20.04"
guest-arch = "x86"
description = """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)`"""
reproduce = """1. Execute the command "perf bench futex lock-pi" in amd64 docker image on s390x
2.
3."""
additional = """"""
|