Re: [PATCH v5 16/16] KVM: x86/xen: Add event channel interrupt vector upcall

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 29/01/21 18:33, David Woodhouse wrote:
On Thu, 2021-01-28 at 13:43 +0100, Paolo Bonzini wrote:
Independent of the answer to the above, this is really the only place
where you're adding Xen code to a hot path.  Can you please use a
STATIC_KEY_FALSE kvm_has_xen_vcpu (and a static inline function) to
quickly return from kvm_xen_has_interrupt() if no vCPU has a shared info
set up?

Something like this, then?

 From 6504c78f76efd8c60630959111bd77c28d43fca7 Mon Sep 17 00:00:00 2001
From: David Woodhouse <dwmw@xxxxxxxxxxxx>
Date: Fri, 29 Jan 2021 17:30:40 +0000
Subject: [PATCH] KVM: x86/xen: Add static branch to avoid overhead of checking
  Xen upcall vector

Signed-off-by: David Woodhouse <dwmw@xxxxxxxxxxxx>

Yes, that was the idea.  Thanks!

Paolo




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux