On 02/18/2014 04:22 PM, Takuya Yoshikawa wrote: > When this was introduced, kvm_flush_remote_tlbs() could be called > without holding mmu_lock. It is now acknowledged that the function > must be called before releasing mmu_lock, and all callers have already > been changed to do so. > I have already posted the patch to moving flush tlb out of mmu-lock when do dirty tracking: KVM: MMU: flush tlb out of mmu lock when write-protect the sptes Actually some patches (patch 1 - patch 4) in that patchset can be pickup-ed separately and i should apologize for the patchset was not updated for a long time since i was busy on other development. And moving tlb flush out of mmu-lock should be going on in the future, so i think the B patch is more acceptable. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
