diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/hypervisor/1111 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1111')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/1111 | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1111 b/results/classifier/deepseek-2-tmp/output/hypervisor/1111 deleted file mode 100644 index b7cbf51de..000000000 --- a/results/classifier/deepseek-2-tmp/output/hypervisor/1111 +++ /dev/null @@ -1,19 +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: - |