From d0c85e36e4de67af628d54e9ab577cc3fad7796a Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Thu, 3 Jul 2025 07:27:52 +0000 Subject: add deepseek and gemma results --- results/classifier/gemma3:12b/kernel/1111 | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 results/classifier/gemma3:12b/kernel/1111 (limited to 'results/classifier/gemma3:12b/kernel/1111') diff --git a/results/classifier/gemma3:12b/kernel/1111 b/results/classifier/gemma3:12b/kernel/1111 new file mode 100644 index 00000000..b7cbf51d --- /dev/null +++ b/results/classifier/gemma3:12b/kernel/1111 @@ -0,0 +1,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: + -- cgit 1.4.1