blob: cc45937f179720e1185f1afc48bd67cd31de9d3d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to figure out whether this bug report is user-mode or system-mode related in QEMU.
The issue is about adding a new syscall (number 436) to the MIPS target in QEMU's user mode. The user added an entry for `sys_getdents64_x32` but encountered ENOSYS, meaning the syscall isn't recognized.
Looking at the code, the MIPS and ARM implementations handle syscalls differently. ARM uses a base number (`ARM_NR_BASE`) to map syscalls, while MIPS doesn't have such a mechanism, leading to potential issues when adding new syscalls beyond the predefined range.
The problem arises in `cpu_loop.c`, which is part of user-mode emulation. User-mode handles running unprivileged applications and system calls made by them. Since this issue is about syscall handling and not involving higher privileges or hardware devices, it's a user-mode problem.
So, the classification should be 'user'.
</think>
user
|