summaryrefslogtreecommitdiffstats
path: root/lib/lzo
diff options
context:
space:
mode:
authorEric Auger <eric.auger@redhat.com>2016-07-22 16:20:41 +0000
committerMarc Zyngier <marc.zyngier@arm.com>2016-07-22 18:52:01 +0100
commit180ae7b1182344ca617d8b5200306b02a6b5075d (patch)
tree927863bc629927451b925be0a483ec9e57307cd3 /lib/lzo
parentd9565a7399d665fa7313122504778cb3d5ef3e19 (diff)
downloadop-kernel-dev-180ae7b1182344ca617d8b5200306b02a6b5075d.zip
op-kernel-dev-180ae7b1182344ca617d8b5200306b02a6b5075d.tar.gz
KVM: arm/arm64: Enable irqchip routing
This patch adds compilation and link against irqchip. Main motivation behind using irqchip code is to enable MSI routing code. In the future irqchip routing may also be useful when targeting multiple irqchips. Routing standard callbacks now are implemented in vgic-irqfd: - kvm_set_routing_entry - kvm_set_irq - kvm_set_msi They only are supported with new_vgic code. Both HAVE_KVM_IRQCHIP and HAVE_KVM_IRQ_ROUTING are defined. KVM_CAP_IRQ_ROUTING is advertised and KVM_SET_GSI_ROUTING is allowed. So from now on IRQCHIP routing is enabled and a routing table entry must exist for irqfd injection to succeed for a given SPI. This patch builds a default flat irqchip routing table (gsi=irqchip.pin) covering all the VGIC SPI indexes. This routing table is overwritten by the first first user-space call to KVM_SET_GSI_ROUTING ioctl. MSI routing setup is not yet allowed. Signed-off-by: Eric Auger <eric.auger@redhat.com> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'lib/lzo')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud