blob: e6d3b778fd2fe37cac65d90e2e1dcb79b4dc359f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I have this bug report about QEMU not setting the MIPS MSA feature in the ELF auxiliary vectors. Let me try to break this down.
First, what's the context? The user is talking about the ELF auxiliary vector and specifically the AT_HWCAP key. They mention that on a MIPS CPU with MSA support, querying this should have the second bit set because HWCAP_MIPS_MSA is 1 << 1. So the problem is that QEMU isn't setting this correctly.
Now, I need to classify this bug as either 'user-mode' or 'system-mode'. User-mode issues are related to applications running in user space, while system-mode involves higher privileges like kernel operations, device drivers, etc.
In this case, the issue is with how QEMU emulates the CPU's capabilities for processes. When a program runs under QEMU and uses MIPS MSA instructions, it relies on the auxiliary vector to know if MSA is supported. If this isn't set correctly, applications might not utilize MSA even if it's available.
Since this affects how user-space applications interact with the emulated CPU, it seems like a user-mode issue. The problem doesn't directly involve kernel operations or device drivers but rather how the environment for user programs is set up in QEMU.
</think>
user
|