diff options
author | 2025-02-25 17:29:24 +0000 | |
---|---|---|
committer | 2025-03-03 14:57:10 -0800 | |
commit | 201c8d40dde900719e9dc1548698e18195f46443 (patch) | |
tree | 6fe6c67ad4932ee87f998049331c0f7a7cc4bc11 /scripts/lib/kdoc/kdoc_output.py | |
parent | KVM: arm64: nv: Handle L2->L1 transition on interrupt injection (diff) | |
download | linux-rng-201c8d40dde900719e9dc1548698e18195f46443.tar.xz linux-rng-201c8d40dde900719e9dc1548698e18195f46443.zip |
KVM: arm64: nv: Add Maintenance Interrupt emulation
Emulating the vGIC means emulating the dreaded Maintenance Interrupt.
This is a two-pronged problem:
- while running L2, getting an MI translates into an MI injected
in the L1 based on the state of the HW.
- while running L1, we must accurately reflect the state of the
MI line, based on the in-memory state.
The MI INTID is added to the distributor, as expected on any
virtualisation-capable implementation, and further patches
will allow its configuration.
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20250225172930.1850838-11-maz@kernel.org
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions