blob: 4dab2841e7fd0d6f5e9f484fab5bfc8aa145a249 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, so I have this bug report to classify as either user-mode or system-mode. The report is about adding a '--targets' option to the qemu-binfmt-conf.sh script. Let me think through this step by step.
First, I need to understand what qemu-binfmt-conf.sh does. From what I know, binfmt_misc is a Linux kernel feature that allows users to register interpreters for binary formats. This means when you try to run an executable of a certain type (like a different architecture), the kernel knows to use a specific interpreter (like QEMU) to handle it. So this script is configuring those interpreters.
The patch adds a '--targets' option, which allows users to specify only certain architectures to register instead of all available ones. This seems like a way to control which binary formats are handled by QEMU.
Now, considering the classification: user-mode vs system-mode. User-mode issues typically relate to processes running without special privileges, while system-mode involves higher-privilege operations, often interacting with hardware or core OS functions.
Since this script is dealing with binfmt_misc, which is a kernel feature that requires setting up binary formats and their interpreters, it's likely handling lower-level configuration. Registering these interpreters probably needs root access because modifying kernel-level settings isn't something regular users can do without privileges.
So the addition of '--targets' is about controlling how QEMU registers itself with the kernel to handle different architectures. This involves system-level configuration because it affects how the kernel handles executables and uses resources like QEMU, which might interact with hardware emulations or device handling.
Therefore, this bug report seems related to system-mode operations.
</think>
system
|