diff options
| author | Oliver Upton <[email protected]> | 2025-05-23 19:47:21 +0000 |
|---|---|---|
| committer | Marc Zyngier <[email protected]> | 2025-05-30 08:11:29 +0000 |
| commit | 4bf3693d36af9768c9bcc1df3a12d00ad6ea8083 (patch) | |
| tree | 3cec9aa699780c776435ca8f6ca115e9df023c73 /rust/helpers | |
| parent | KVM: arm64: Resolve vLPI by host IRQ in vgic_v4_unset_forwarding() (diff) | |
| download | kernel-4bf3693d36af9768c9bcc1df3a12d00ad6ea8083.tar.gz kernel-4bf3693d36af9768c9bcc1df3a12d00ad6ea8083.zip | |
KVM: arm64: Unmap vLPIs affected by changes to GSI routing information
KVM's interrupt infrastructure is dodgy at best, allowing for some ugly
'off label' usage of the various UAPIs. In one example, userspace can
change the routing entry of a particular "GSI" after configuring
irqbypass with KVM_IRQFD. KVM/arm64 is oblivious to this, and winds up
preserving the stale translation in cases where vLPIs are configured.
Honor userspace's intentions and tear down the vLPI mapping if affected
by a "GSI" routing change. Make no attempt to reconstruct vLPIs if the
new target is an MSI and just fall back to software injection.
Tested-by: Sweet Tea Dorminy <[email protected]>
Signed-off-by: Oliver Upton <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Marc Zyngier <[email protected]>
Diffstat (limited to 'rust/helpers')
0 files changed, 0 insertions, 0 deletions