On Tue, Aug 18, 2020 at 08:31:08AM +0200, Paolo Bonzini wrote: > On 11/08/20 12:27, Will Deacon wrote: > > Will Deacon (2): > > KVM: Pass MMU notifier range flags to kvm_unmap_hva_range() > > KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not set > > > > arch/arm64/include/asm/kvm_host.h | 2 +- > > arch/arm64/kvm/mmu.c | 19 ++++++++++++++----- > > arch/mips/include/asm/kvm_host.h | 2 +- > > arch/mips/kvm/mmu.c | 3 ++- > > arch/powerpc/include/asm/kvm_host.h | 3 ++- > > arch/powerpc/kvm/book3s.c | 3 ++- > > arch/powerpc/kvm/e500_mmu_host.c | 3 ++- > > arch/x86/include/asm/kvm_host.h | 3 ++- > > arch/x86/kvm/mmu/mmu.c | 3 ++- > > virt/kvm/kvm_main.c | 3 ++- > > 10 files changed, 30 insertions(+), 14 deletions(-) > > > > These would be okay for 5.9 too, so I plan to queue them myself before > we fork for 5.10. Thanks, Paolo. Let me know if you want me to rebase/repost. Please note that I'm planning on rewriting most of the arm64 KVM page-table code for 5.10, so if you can get this series in early (e.g. for -rc2), then it would _really_ help with managing the kvm/arm64 queue for the next merge window. Otherwise, could you and Marc please set up a shared branch with just these, so I can use it as a base? Please let me know. Will _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
