KVM: x86: hyper-v: XMM fast hypercalls fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | KVM: x86: hyper-v: Drop redundant 'ex' parameter from kvm_hv_send_ipi()arch/ | +4 | 3 replies | |
| 2/4 | KVM: x86: hyper-v: Drop redundant 'ex' parameter from kvm_hv_flush_tlb()arch/ | +6 | 2 replies | |
| 3/4 | KVM: x86: hyper-v: Fix the maximum number of sparse banks for XMM fast TLB flush hypercallsarch/ | +2 | 1 reply | |
| 4/4 | KVM: x86: hyper-v: HVCALL_SEND_IPI_EX is an XMM fast hypercallarch/ | +34 | 3 replies |
Reviews trailers per patch
All 4 patches have a Reviewed-by or Acked-by.
| Patch | Maxim Levitsky | Siddharth Chandrasekaran |
|---|---|---|
| 1/4 | R-b | R-b |
| 2/4 | R-b | R-b |
| 3/4 | R-b | |
| 4/4 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] KVM: x86: hyper-v: XMM fast hypercalls fixes
While working on some Hyper-V TLB flush improvements and Direct TLB flush feature for Hyper-V on KVM I experienced Windows Server 2019 crashes on boot when XMM fast hypercall input feature is advertised. Turns out, HVCALL_SEND_IPI_EX is also an XMM fast hypercall and returning an error kills the guest. This is fixed in PATCH4. PATCH3 fixes erroneous capping of sparse CPU banks for XMM fast TLB flush hypercalls. The problem should be reproducible with >360 vCPUs.
Vitaly Kuznetsov (4):
KVM: x86: hyper-v: Drop redundant 'ex' parameter from
kvm_hv_send_ipi()
KVM: x86: hyper-v: Drop redundant 'ex' parameter from
kvm_hv_flush_tlb() KVM: x86: hyper-v: Fix the maximum number of sparse banks for XMM fast
TLB flush hypercalls
KVM: x86: hyper-v: HVCALL_SEND_IPI_EX is an XMM fast hypercall
arch/x86/kvm/hyperv.c | 84 +++++++++++++++++++++++-------------------- 1 file changed, 45 insertions(+), 39 deletions(-)
Signature · 1 line
2.35.1