diff options
| author |   Yi Wang <foxywang@tencent.com> | 2024-05-06 18:17:51 +0800 |
|---|---|---|
| committer |   Sean Christopherson <seanjc@google.com> | 2024-06-11 14:18:41 -0700 |
| commit | c4201bd24f4ae80760ecdcf6c0d261ca867ba4ca (patch) | |
| tree | 522350a79b805a685d1d9c3f971099704328bb07 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | KVM: x86: Don't re-setup empty IRQ routing when KVM_CAP_SPLIT_IRQCHIP (diff) | |
| download | wireguard-linux-c4201bd24f4ae80760ecdcf6c0d261ca867ba4ca.tar.xz wireguard-linux-c4201bd24f4ae80760ecdcf6c0d261ca867ba4ca.zip | |
KVM: s390: Don't re-setup dummy routing when KVM_CREATE_IRQCHIP
Now that KVM sets up empty irq routing in kvm_create_vm(), there's
no need to setup dummy routing when KVM_CREATE_IRQCHIP.
Note, userspace could very theoretically use KVM_CREATE_IRQCHIP after
KVM_SET_GSI_ROUTING to reset to empty IRQ routing, but it's extremely
unlikely any VMM does that, e.g. the main reason s390 does anything for
KVM_CREATE_IRQCHIP is to that s390 doesn't need to be special cased by the
VMM.
Signed-off-by: Yi Wang <foxywang@tencent.com>
Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Link: https://lore.kernel.org/r/20240506101751.3145407-4-foxywang@tencent.com
[sean: keep use_irqchip check, call out KVM_SET_GSI_ROUTING impact]
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions