diff options
author | Andre Przywara <andre.przywara@arm.com> | 2016-07-15 13:43:37 +0200 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2016-07-18 19:14:38 +0200 |
commit | 2891a7dfb6c4a273996f0047660a75e88e3b8690 (patch) | |
tree | d703ea96114d917700aa5091c8287e844ce1b789 /Documentation/virtual | |
parent | KVM: arm64: vgic-its: Implement ITS command queue command handlers (diff) | |
download | linux-2891a7dfb6c4a273996f0047660a75e88e3b8690.tar.xz linux-2891a7dfb6c4a273996f0047660a75e88e3b8690.zip |
KVM: arm64: vgic-its: Implement MSI injection in ITS emulation
When userland wants to inject an MSI into the guest, it uses the
KVM_SIGNAL_MSI ioctl, which carries the doorbell address along with
the payload and the device ID.
With the help of the KVM IO bus framework we learn the corresponding
ITS from the doorbell address. We then use our wrapper functions to
iterate the linked lists and find the proper Interrupt Translation Table
Entry (ITTE) and thus the corresponding struct vgic_irq to finally set
the pending bit.
We also provide the handler for the ITS "INT" command, which allows a
guest to trigger an MSI via the ITS command queue. Since this one knows
about the right ITS already, we directly call the MMIO handler function
without using the kvm_io_bus framework.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Tested-by: Eric Auger <eric.auger@redhat.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'Documentation/virtual')
0 files changed, 0 insertions, 0 deletions