blob: f60c977811967caf96e57912fe27e31bd0c1ae28 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, so I'm trying to classify this bug report regarding QEMU as either user-mode or system-mode related. The issue is about an option to constrain the Linux-user exec() function to an emulated CPU only.
First, I need to understand what each mode entails. User-mode emulation in QEMU typically deals with running applications without a full OS, focusing on the execution of user-space programs. It allows you to run binaries compiled for different architectures on your host system. System-mode, on the other hand, involves emulating an entire computer system, including the kernel and peripherals.
The bug report mentions constraining exec() in Linux-user. The exec() function is used to execute a new program in the current process space, which is definitely part of user-space operations. Since this option affects how user applications are executed within the emulator, it doesn't seem to involve higher privileges or system-level components like device emulation.
Therefore, this issue is related to user-mode because it pertains to executing user-space programs and controlling their execution environment without delving into kernel or hardware emulation.
</think>
user
|