[PATCH v5 0/5] KVM: x86: hyperv: PV IPI support for Windows guests

[Vitaly Kuznetsov <vkuznets@redhat.com>]

Changes since v4:
- Rebase to the current kvm/next (KVM_CAP_HYPERV_SEND_IPI is now 159)
- Use 64 instead of 'BITS_PER_LONG' [Roman Kagan]
- Continue in case wrong VP ids or disabled APICs instead of bailing
  [Roman Kagan]

Using hypercall for sending IPIs is faster because this allows to specify
any number of vCPUs (even > 64 with sparse CPU set), the whole procedure
will take only one VMEXIT.

Same as PV TLB flush, this allows Windows guests having > 64 vCPUs to boot
on KVM when Hyper-V extensions are enabled.

Vitaly Kuznetsov (5):
  KVM: x86: hyperv: enforce vp_index < KVM_MAX_VCPUS
  KVM: x86: hyperv: optimize 'all cpus' case in kvm_hv_flush_tlb()
  KVM: x86: hyperv: use get_vcpu_by_vpidx() in kvm_hv_flush_tlb()
  x86/hyper-v: rename ipi_arg_{ex,non_ex} structures
  KVM: x86: hyperv: implement PV IPI send hypercalls

 Documentation/virtual/kvm/api.txt  |   7 ++
 arch/x86/hyperv/hv_apic.c          |   8 +-
 arch/x86/include/asm/hyperv-tlfs.h |  16 +--
 arch/x86/kvm/hyperv.c              | 201 +++++++++++++++++++++++++++----------
 arch/x86/kvm/trace.h               |  42 ++++++++
 arch/x86/kvm/x86.c                 |   1 +
 include/uapi/linux/kvm.h           |   1 +
 virt/kvm/kvm_main.c                |   6 +-
 8 files changed, 214 insertions(+), 68 deletions(-)

-- 
2.14.4