Paolo Bonzini <pbonzini@xxxxxxxxxx> writes: > These are the patches that are still on my list: > > * https://patchew.org/linux/20221105045704.2315186-1-vipinsh@xxxxxxxxxx/ > [PATCH 0/6] Add Hyper-v extended hypercall support in KVM > > * https://patchew.org/linux/20221019165618.927057-1-seanjc@xxxxxxxxxx/ > [PATCH v6 0/8] KVM: x86: Apply NX mitigation more precisely > > * https://patchew.org/linux/20221004093131.40392-1-thuth@xxxxxxxxxx/ > [RFC PATCH 0/3] Use TAP in some more KVM selftests > > * https://patchew.org/linux/20221012181702.3663607-1-seanjc@xxxxxxxxxx/ > [PATCH v4 00/11] KVM: x86/mmu: Make tdp_mmu a read-only parameter > > * https://patchew.org/linux/20221001005915.2041642-1-seanjc@xxxxxxxxxx/ > [PATCH v4 00/32] KVM: x86: AVIC and local APIC fixes+cleanups > > > Of which only the last one *might* be delayed to 6.3. > > Sean, if you have anything else feel free to collect them yourself and > send a pull request. My "shameless plug" here would be: "[PATCH v2 0/4] KVM: VMX: nVMX: Make eVMCS enablement more robust" (https://lore.kernel.org/kvm/20221104144708.435865-1-vkuznets@xxxxxxxxxx/). it doesn't add any new features, however, is intended to make KVM-on-Hyper-V enablement "future proof" against possible changes in future Hyper-V versions. -- Vitaly
