blob: 8d1082ce3bf760a9f9a47e539fe0df548f87d0c2 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I need to classify this QEMU bug report as either a user-mode issue or a system-mode issue. Let me think through the information provided.
The problem occurs in both qemu-system-mips and mips-linux-user. In system mode, it's hanging when running a Debian MIPS guest with specific commands. The error messages mention unhandled CPU exceptions and GPR registers, which suggests that it's dealing with low-level processor states.
In user mode, the issue arises when executing a compiled C program that runs invalid instructions, leading to an exception. This indicates that the problem is occurring at the level of individual process execution rather than system-wide operations.
So, considering that the issue affects both modes but the details point towards CPU instruction handling and exceptions which are core to how the emulator processes user space programs, I think this falls under user-mode.
</think>
The bug report involves issues with executing invalid instructions in a MIPS emulation environment. It's observed in both system-mode (qemu-system-mips) and user-mode (mips-linux-user). However, since the problem pertains to handling CPU exceptions during instruction execution, which is fundamental to process-level operations rather than system-wide or device-related tasks, it is classified as a 'user' mode issue.
user
|