Message ID | 20220803134110.397885-1-vkuznets@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | KVM: x86: hyper-v: Fine-grained TLB flush + L2 TLB flush features | expand |
Vitaly Kuznetsov <vkuznets@redhat.com> writes: > Changes since v8: > - Rebase to the current kvm/queue (93472b797153) > - selftests: move Hyper-V test pages to a dedicated struct untangling from > vendor-specific (VMX/SVM) pages allocation [Sean]. Sean, Paolo, I've jsut checked and this series applies cleanly on top of the latest kvm/queue [372d07084593]. I also don't seem to have any feedback to address. Any chance this can be queued?
On Tue, Aug 30, 2022, Vitaly Kuznetsov wrote: > Vitaly Kuznetsov <vkuznets@redhat.com> writes: > > > Changes since v8: > > - Rebase to the current kvm/queue (93472b797153) > > - selftests: move Hyper-V test pages to a dedicated struct untangling from > > vendor-specific (VMX/SVM) pages allocation [Sean]. > > Sean, Paolo, > > I've jsut checked and this series applies cleanly on top of the latest > kvm/queue [372d07084593]. I also don't seem to have any feedback to > address. > > Any chance this can be queued? It's the top "big" series on my todo list. I fully plan on getting queued for 6.1, but I don't expect to get to it this week.
Sean Christopherson <seanjc@google.com> writes: > On Tue, Aug 30, 2022, Vitaly Kuznetsov wrote: >> Vitaly Kuznetsov <vkuznets@redhat.com> writes: >> >> > Changes since v8: >> > - Rebase to the current kvm/queue (93472b797153) >> > - selftests: move Hyper-V test pages to a dedicated struct untangling from >> > vendor-specific (VMX/SVM) pages allocation [Sean]. >> >> Sean, Paolo, >> >> I've jsut checked and this series applies cleanly on top of the latest >> kvm/queue [372d07084593]. I also don't seem to have any feedback to >> address. >> >> Any chance this can be queued? > > It's the top "big" series on my todo list. I fully plan on getting queued for 6.1, > but I don't expect to get to it this week. I was going to do a bare 'ping' here but then I decided to check whether this series still applies cleanly and turns out there's some fuzz and some minor conflicts with the already queued "KVM: VMX: Support updated eVMCSv1 revision + use vmcs_config for L1 VMX MSRs" (in sean/for_paolo/6.1 atm). I've rebased and re-tested and besides the (unrelated) shadow MMU issue I've reported, things still seem to work fine. I'm going to go ahead and send out rebased v10 then.