blob: b5f8039b98936bfc008570fbbd805a8a20b42ba7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to figure out whether this bug report about QEMU is related to user mode or system mode. Let me break it down.
The problem is that when building QEMU using a patched version of Ninja that's supposed to support make's jobserver feature, only one CPU/core is being used instead of the expected four. The steps involve modifying the Makefile to remove filtering of -j arguments so that multiple jobs can run in parallel.
From what I understand, user-mode issues usually relate to how applications behave or are built, especially when they don't require special privileges. System-mode issues typically involve lower-level stuff like device drivers, hardware access, or kernel interactions which might need higher privileges.
In this case, the problem is about build configuration and job handling using make and ninja. It doesn't seem to be related to running QEMU in a virtualized environment or interacting with system resources beyond the build process itself. So it's more about how the software is compiled rather than how it runs as a system service.
Therefore, I think this bug is user-mode related because it's about the build setup and parallel job execution during compilation.
</think>
user
|