blob: 604fced85fe7cad6009886c8b0e1fd742bc1f5a7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I'm trying to classify this bug report for QEMU as either user-mode or system-mode related. Let's see what information I have here.
First, the issue is about a stack overflow in address_space_stl_internal. The reproducers involve using specific commands that seem to interact with USB devices and memory operations. Looking at the stack trace, it mentions functions like xhci_intr_update and xhci_runtime_write, which are part of the xHCI (USB host controller) implementation.
I know that QEMU has two main modes: user-mode and system-mode emulation. User-mode is for running unprivileged applications, while system-mode deals with emulating entire systems including peripherals, devices, and higher-privilege operations.
The functions involved here, like memory_region_write_accessor and address_space_translate, are part of the memory management in QEMU's softmmu (software MMU) layer. These are typically used in system-mode emulation where hardware-level details and device interactions are handled.
Also, looking at the commands in the reproducer, they set up a machine with specific devices like qemu-xhci and usb-tablet, which are part of emulating a system's hardware environment. This suggests that the issue is occurring during system-level operations rather than user application execution.
Therefore, this bug seems to be related to how QEMU handles memory accesses for device emulation in system-mode, making it a system-mode issue.
</think>
system
|
