blob: 12a44e02fa85778d14c457d5b44503e1c6a5af6c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to figure out whether this bug report about QEMU is related to user-mode or system-mode. The report mentions "Supported ARMv8.? Opcodes." So, it's talking about opcodes in the ARM architecture.
First, understanding what each mode entails: User-mode deals with applications running on a CPU, handling things like instructions execution without needing high privileges. System-mode involves lower-level operations, including device management, peripherals, and operating system functions that require higher privileges.
ARMv8 opcodes are part of the instruction set architecture, which affects how user-space programs execute. Since this is about opcodes, it relates to how the CPU processes instructions in applications, not necessarily dealing with system-level components or devices.
So, the issue seems focused on ensuring that QEMU correctly supports these ARMv8 opcodes for application execution. That points towards a user-mode concern because it's about application-level code rather than system services or hardware interactions.
Therefore, I classify this as 'user' related.
</think>
The bug report focuses on ARMv8 opcode support in QEMU, which pertains to application-level instruction processing without involving higher-privilege operations.
Answer: user
|