blob: 3379d887441aec3b40437d5452896d8c54e8767b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I need to figure out whether this bug report is related to user-mode or system-mode in QEMU. The user is running a Go program inside an ARM environment emulated by QEMU on Ubuntu. The issue occurs when they run "go run test.go" multiple times; sometimes it hangs.
First, looking at the reproduction steps: They ran the command 500 times and it hung around 200-300 times. The test program is a simple loop that prints "Hello world" 1000 times. So it's a straightforward Go program with no complex operations.
The environment includes Ubuntu 16.04, QEMU-arm version 4.2.0, and Go 1.14.1 for ARM. The user provided strace logs, which usually show system calls. Since the issue is happening when running a Go binary, it's more about how the program interacts with the host OS rather than low-level hardware emulation.
Considering QEMU has two main modes: user-mode and system-mode. User-mode handles CPU instruction translation for individual processes, while system-mode emulates an entire system including peripherals and devices.
Since the problem occurs when executing a Go binary (which is a process), it's likely related to how QEMU translates or executes the ARM instructions in user-space. It's not about the OS kernel or device drivers because the program doesn't interact with hardware beyond printing to stdout.
Therefore, this issue falls under 'user-mode' as it pertains to the execution of userland processes.
</think>
The bug report is classified as 'user' because it involves a Go program running in user space, causing QEMU's user-mode emulation to hang.
**Answer:** user
|