Lines Matching full:zap

440 			 * task can zap/remove the SPTE as mmu_lock is held for  in handle_removed_pt()
642 	 * SPTE.  KVM should never attempt to zap or manipulate a FROZEN SPTE,  in __tdp_mmu_set_spte_atomic()
886 	 * Zap roots in multiple passes of decreasing granularity, i.e. zap at  in tdp_mmu_zap_root()
890 	 * the zap, but in most cases the zap itself isn't latency sensitive.  in tdp_mmu_zap_root()
896 	 * allows verifying that KVM can safely zap 1GiB regions, e.g. without  in tdp_mmu_zap_root()
982  * Zap leaf SPTEs for the range of gfns, [start, end), for all *VALID** roots.
1002 	 * Zap all direct roots, including invalid direct roots, as all direct  in kvm_tdp_mmu_zap_all()
1006 	 * Zap directly even if the root is also being zapped by a concurrent  in kvm_tdp_mmu_zap_all()
1007 	 * "fast zap".  Walking zapped top-level SPTEs isn't all that expensive  in kvm_tdp_mmu_zap_all()
1021  * Zap all invalidated roots to ensure all SPTEs are dropped before the "fast
1022  * zap" completes.
1783 		 * Don't zap leaf SPTEs, if a leaf SPTE could be replaced with  in recover_huge_pages_range()