blob: 50da8a1f3b245456978f9178c7e392efe946c5a3 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, I need to figure out whether this bug is user-mode or system-mode related. The issue mentions qemu-user not blocking target signals when entering a signal handler. From what I know, qemu has two main modes: user mode and system mode.
User-mode emulation allows running binaries of one architecture on another without full virtualization. It translates syscalls as they happen. On the other hand, system-mode is for full OS virtualization, handling hardware devices and lower-level operations.
The bug report talks about target signals in a user-space program, which suggests it's related to how QEMU handles signal processing when running an application in user mode. The function process_pending_signals is part of the signal handling in the user-emulation code (linux-user/signal.c). This indicates that the problem occurs within the context of emulating a process, not the full OS or hardware.
Since it's dealing with signals and their handlers which are part of the application's execution, this falls under user-mode. There's no mention of higher-privilege operations, peripherals, or device handling here—just signal processing in user-space.
</think>
user
|