blob: c7d088238f8d3a218d52fce0f1b7d6ec4aca2295 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to figure out whether this QEMU bug is user-mode or system-mode related. The problem occurs when running a MIPS executable that crashes somewhere in tdelete. From the description, it's an issue introduced in the 6.0.0 development cycle and affects both MIPS and Aarch64 executables.
First, I'll look at what user-mode and system-mode entail. User-mode typically deals with emulating the CPU and executing applications without a full OS, while system-mode involves running entire operating systems, including device emulation and higher privileges.
The crash happens in tdelete, which is part of the application's execution, not during OS operations. The user provided pre-built binaries and steps to reproduce involve running the MIPS executable with QEMU. They mentioned building on Ubuntu using cross-compilers, so it's more about running a specific app rather than an entire OS.
Additionally, patches related to this issue were applied to fix Aarch64 by modifying how exceptions are handled in the CPU emulation code (target/arm/translate.h). The MIPS patch similarly targets CPU translation, indicating that the problem is within the user-mode emulation of the CPU instructions.
Since the crash occurs during application execution without mention of OS-level issues like device drivers or kernel panics, it's more aligned with user-mode. There's no indication of higher privileges or peripherals being involved in the crash.
</think>
user
|