From: Yi Wang <up2wing@gmail.com>
To: seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: wanpengli@tencent.com, up2wing@gmail.com, Yi Wang <foxywang@tencent.com>
Subject: [PATCH] KVM: irqchip: synchronize srcu only if needed
Date: Fri, 12 Jan 2024 17:11:28 +0800 [thread overview]
Message-ID: <20240112091128.3868059-1-foxywang@tencent.com> (raw)
From: Yi Wang <foxywang@tencent.com>
We found that it may cost more than 20 milliseconds very accidentally
to enable cap of KVM_CAP_SPLIT_IRQCHIP on a host which has many vms
already.
The reason is that when vmm(qemu/CloudHypervisor) invokes
KVM_CAP_SPLIT_IRQCHIP kvm will call synchronize_srcu_expedited() and
might_sleep and kworker of srcu may cost some delay during this period.
Since this happens during creating vm, it's no need to synchronize srcu
now 'cause everything is not ready(vcpu/irqfd) and none uses irq_srcu now.
Signed-off-by: Yi Wang <foxywang@tencent.com>
---
arch/x86/kvm/irq_comm.c | 2 +-
include/linux/kvm_host.h | 2 ++
virt/kvm/irqchip.c | 3 ++-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/irq_comm.c b/arch/x86/kvm/irq_comm.c
index 16d076a1b91a..37c92b7486c7 100644
--- a/arch/x86/kvm/irq_comm.c
+++ b/arch/x86/kvm/irq_comm.c
@@ -394,7 +394,7 @@ static const struct kvm_irq_routing_entry empty_routing[] = {};
int kvm_setup_empty_irq_routing(struct kvm *kvm)
{
- return kvm_set_irq_routing(kvm, empty_routing, 0, 0);
+ return kvm_set_irq_routing(kvm, empty_routing, 0, NONEED_SYNC_SRCU);
}
void kvm_arch_post_irq_routing_update(struct kvm *kvm)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index 4944136efaa2..a46370cca355 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -1995,6 +1995,8 @@ static inline int mmu_invalidate_retry_hva(struct kvm *kvm,
#define KVM_MAX_IRQ_ROUTES 4096 /* might need extension/rework in the future */
+#define NONEED_SYNC_SRCU (1U << 0)
+
bool kvm_arch_can_set_irq_routing(struct kvm *kvm);
int kvm_set_irq_routing(struct kvm *kvm,
const struct kvm_irq_routing_entry *entries,
diff --git a/virt/kvm/irqchip.c b/virt/kvm/irqchip.c
index 1e567d1f6d3d..cea5c43c1a49 100644
--- a/virt/kvm/irqchip.c
+++ b/virt/kvm/irqchip.c
@@ -224,7 +224,8 @@ int kvm_set_irq_routing(struct kvm *kvm,
kvm_arch_post_irq_routing_update(kvm);
- synchronize_srcu_expedited(&kvm->irq_srcu);
+ if (!(flags & NONEED_SYNC_SRCU))
+ synchronize_srcu_expedited(&kvm->irq_srcu);
new = old;
r = 0;
--
2.39.3
next reply other threads:[~2024-01-12 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:11 Yi Wang [this message]
2024-01-12 16:28 ` Sean Christopherson
2024-01-15 16:01 ` Yi Wang
2024-01-16 16:50 ` Christian Borntraeger
2024-01-16 16:58 ` Sean Christopherson
2024-01-17 0:56 ` Yi Wang
2024-01-17 0:46 ` Yi Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240112091128.3868059-1-foxywang@tencent.com \
--to=up2wing@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=foxywang@tencent.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®