The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1858461
Title:
Please refactor linux-user/mips/cpu_loop.c
Status in QEMU:
Incomplete
Bug description:
Hello. I am working with qemu on test images. I've added a new syscall
(436) to qemu but received ENOSYS from mips application.
Please open "linux-user/mips/cpu_loop.c". I've added at the end of
"mips_syscall_args" the following:
```
MIPS_SYS(sys_getdents64_x32, 3)
```
But
```
syscall_num = env->active_tc.gpr[2] - 4000;
if (syscall_num >= sizeof(mips_syscall_args)) {
ret = -TARGET_ENOSYS;
```
returns -TARGET_ENOSYS
We can see that "linux-user/mips/cpu_loop.c" differs a lot from
"linux-user/arm/cpu_loop.c". Arm has it's own "ARM_NR_BASE" and etc.
Can you please refactor mips cpu loop in the same way as arm? Thank
you.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1858461/+subscriptions
