1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I need to classify this bug report into one of the given categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The bug report is about RISC-V AIA compliance tests failing in QEMU but passing on hardware. The specific issues mentioned are at Interrupt filtering and virtual interrupts for supervisor level.
Let me break this down. RISC-V AIA relates to interrupt handling mechanisms in the RISC-V architecture, specifically designed for managing interrupts efficiently. In QEMU, which is an emulator and a hypervisor, how are these interrupts handled?
The user mentioned that the tests pass on hardware but fail in QEMU. This suggests there might be an issue with how QEMU emulates or handles interrupt-related functionalities compared to real hardware.
Looking at the categories, 'hypervisor' seems relevant because QEMU acts as a hypervisor when running virtual machines. Issues related to interrupt handling could stem from how the hypervisor manages virtualization of interrupts, possibly affecting guest OS behavior.
Other possible categories: device? Well, devices might relate more to specific hardware emulations, but since this is about interrupt architecture at the supervisor level, it's more system-level and tied to the hypervisor's management. So 'hypervisor' seems like the best fit.
</think>
hypervisor
|