blob: 6fab40631b2a4b3550ae4d3aedebd3121d4335ae (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, I'm trying to figure out whether this QEMU AARCH64 bug is a user-mode or system-mode issue. So the report says that QEMU's AARCH64 emulation doesn't support canonical addresses when running on x86_64.
First, I need to understand what each mode entails. User-mode involves processes and applications running under the operating system, handling things like process scheduling and memory management for individual apps. System-mode deals with lower-level stuff like hardware devices, peripherals, and the OS itself.
In this case, the issue is about QEMU's support for AARCH64 addresses on an x86_64 host. Since QEMU is an emulator that runs entire systems (like virtual machines), it handles the low-level details of different architectures. Canonical addresses are related to how memory addresses are handled in ARM systems, which is a lower-level concern.
So this problem seems to involve the way QEMU emulates the hardware and memory structure for AARCH64 on x86_64 hosts. That makes me think it's more about system-mode because it's dealing with the architecture level rather than individual user applications.
</think>
system
|