On 2018-11-13 at 10:36 David Hildenbrand <david@xxxxxxxxxx> wrote: > > Note that KVM already faulted in the page (or huge page) in the host's > > page table, and we hold the KVM mmu spinlock (grabbed before checking > > the mmu seq). > > I wonder if the KVM mmu spinlock is enough for walking (not KVM > exclusive) host page tables. Can you elaborate? I'll update the commit message with the info from Paolo's email (about kvm_mmu_notifier_invalidate_range_end()). Thanks, Barret
