1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
<think>
Okay, so I'm trying to figure out whether this bug report about QEMU is related to user-mode or system-mode issues. Let me break down what's happening here.
The problem seems to be that when running certain programs under QEMU in user mode for some architectures like PPC, S390X, and SPARC64, the handling of the SIGSEGV signal isn't working as expected. On real hardware, these programs run fine and exit with code 0, but under QEMU emulation, they either return an error code or cause a segmentation fault.
The user mentions that the documentation says QEMU in user mode supports POSIX signal handling. However, for some architectures (ppc, ppc64, etc.), catching SIGSEGV doesn't work as it does on others like aarch64 or arm. This suggests there's an issue with how signals are being handled by QEMU when emulating these specific architectures.
Looking at the details:
- For PPC and others, the program exits with code 3 instead of 0.
- On S390X, it mentions that the Linux kernel truncates the fault address in 'si_addr', but QEMU doesn't do this, causing compatibility issues. However, when a specific flag is used to avoid this behavior, it works correctly.
- For SPARC64, running under QEMU causes a segmentation fault with a core dump.
This makes me think that the issue lies within how QEMU is handling signals in user mode for these architectures. Since user-mode emulation deals with translating system calls and signals from the guest program to the host environment, any discrepancies here would affect signal handling directly.
System-mode issues typically involve higher privileges, devices, peripherals, or the OS running on top of QEMU. But this problem seems more about how signals are being processed within the emulated process itself, which points towards a user-mode issue.
So, considering all that, I think this bug is related to user-mode in QEMU because it's about signal handling within processes rather than system-level operations or device emulation.
</think>
user
|