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 January 2021 19:19:55 GMT, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote:
>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?
>> 
>
>Yes, that was the idea.  Thanks!

Ok, I'll take a look at the get/set ioctls, maybe post an incremental patch for those to get confirmation, then rework it all into the series and repost based on kvm/next.

Thanks.


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.




[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