summaryrefslogtreecommitdiffstats
path: root/arch/x86/kvm/irq.c
diff options
context:
space:
mode:
authorYi Wang <foxywang@tencent.com>2024-05-06 12:17:49 +0200
committerSean Christopherson <seanjc@google.com>2024-06-11 23:18:34 +0200
commitfbe4a7e881d4408bfabbb4fd538f10fd686cd8ab (patch)
tree104d9dd3cfe88d4f5b9a9c713f483aecf9d6bcd0 /arch/x86/kvm/irq.c
parentKVM: fix documentation rendering for KVM_CAP_VM_MOVE_ENC_CONTEXT_FROM (diff)
downloadlinux-fbe4a7e881d4408bfabbb4fd538f10fd686cd8ab.tar.xz
linux-fbe4a7e881d4408bfabbb4fd538f10fd686cd8ab.zip
KVM: Setup empty IRQ routing when creating a VM
Setup empty IRQ routing during VM creation so that x86 and s390 don't need to set empty/dummy IRQ routing during KVM_CREATE_IRQCHIP (in future patches). Initializing IRQ routing before there are any potential readers allows KVM to avoid the synchronize_srcu() in kvm_set_irq_routing(), which can introduces 20+ milliseconds of latency in the VM creation path. Ensuring that all VMs have non-NULL IRQ routing also hardens KVM against misbehaving userspace VMMs, e.g. RISC-V dynamically instantiates its interrupt controller, but doesn't override kvm_arch_intc_initialized() or kvm_arch_irqfd_allowed(), and so can likely reach kvm_irq_map_gsi() without fully initialized IRQ routing. Signed-off-by: Yi Wang <foxywang@tencent.com> Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com> Link: https://lore.kernel.org/r/20240506101751.3145407-2-foxywang@tencent.com [sean: init refcount after IRQ routing, fix stub, massage changelog] Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'arch/x86/kvm/irq.c')
0 files changed, 0 insertions, 0 deletions