blob: e2052fd7ea10d46fe6420d2ad87b7c9aadbde4ba (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I'm trying to figure out whether this bug report is related to user-mode or system-mode in QEMU. Let's break it down.
The issue involves the aarch64 SVE (Scalable Vector Extensions) emulation breaking certain string functions like strnlen and strrchr when using QEMU version 5.2.0. The test cases pass when the CPU is set to 'max' with 'sve-max-vq=2', but they fail otherwise.
The user provided a link to their GitHub repository for ARM optimized routines, specifically pointing out that native compilation works, which suggests it's not an issue with their code. They mentioned running tests using QEMU, implying the problem occurs in the emulator environment.
QEMU has two main modes: user-mode and system-mode. User-mode emulation allows running applications without a full OS, while system-mode emulates a complete system, including hardware devices and an OS. Since this bug is about string functions failing during execution of a test binary under QEMU, it seems to be related to how the CPU instructions are being emulated in user-mode.
The fact that setting 'sve-max-vq=2' fixes the issue points towards vector length configuration in the emulator. This tweak affects SVE's behavior, which is part of the CPU instruction set, not the system devices or OS setup. So, it's more about how QEMU handles SVE instructions when emulating user-mode processes.
Therefore, I think this bug falls under user-mode because it relates to the execution of application code and CPU instruction emulation rather than higher-level system components.
</think>
user
|