diff options
| author |   Yi Wang <foxywang@tencent.com> | 2024-05-06 18:17:50 +0800 |
|---|---|---|
| committer |   Sean Christopherson <seanjc@google.com> | 2024-06-11 14:18:40 -0700 |
| commit | e3c89f5dd11df791b55b320c3869a97414ef5d06 (patch) | |
| tree | ed6d459e43724ce9c490ecadbdb12979ea340588 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: Setup empty IRQ routing when creating a VM (diff) | |
| download | linux-rng-e3c89f5dd11df791b55b320c3869a97414ef5d06.tar.xz linux-rng-e3c89f5dd11df791b55b320c3869a97414ef5d06.zip | |
KVM: x86: Don't re-setup empty IRQ routing when KVM_CAP_SPLIT_IRQCHIP
Now that KVM sets up empty IRQ routing during VM creation, don't recreate
empty routing during KVM_CAP_SPLIT_IRQCHIP. Setting IRQ routes during
KVM_CAP_SPLIT_IRQCHIP can result in 20+ milliseconds of delay due to the
synchronize_srcu_expedited() call in kvm_set_irq_routing().
Note, the empty routing is guaranteed to be intact as KVM x86 only allows
changing the IRQ routing after an in-kernel IRQCHIP has been created, and
KVM_CAP_SPLIT_IRQCHIP is disallowed after creating an IRQCHIP.
Signed-off-by: Yi Wang <foxywang@tencent.com>
Link: https://lore.kernel.org/r/20240506101751.3145407-3-foxywang@tencent.com
[sean: massage changelog, remove unused empty_routing array]
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions