kvm/mmu/mmu.c

1392 	 * of memslot has no such restriction, so the range can cross two large
1897 	 * differs then the memslot lookup (SMM vs. non-SMM) will be bogus, the
3051 	 * Note, using the already-retrieved memslot and __gfn_to_hva_memslot()
3056 	 * read-only memslot.
3750 			 * were made now versus when the memslot was created.
4371 	 * Retry the page fault if the gfn hit a memslot that is being deleted
4372 	 * or moved.  This ensures any existing SPTEs for the old memslot will
4457  * root was invalidated by a memslot update or a relevant mmu_notifier fired.
5660 	 *  (b) remote reloads due to a memslot update obsoletes _all_ roots
5664 	 * Note!  Dummy roots are unique in that they are obsoleted by memslot
6268  * It's required when memslot is being deleted or VM is being
6314 	 * returning to the caller, e.g. if the zap is in response to a memslot
6316 	 * associated with the deleted memslot once the update completes, and
6366 	const struct kvm_memory_slot *memslot;
6380 			memslot = iter.slot;
6381 			start = max(gfn_start, memslot->base_gfn);
6382 			end = min(gfn_end, memslot->base_gfn + memslot->npages);
6386 			flush = __walk_slot_rmaps(kvm, memslot, __kvm_zap_rmap,
6433 				      const struct kvm_memory_slot *memslot,
6438 		walk_slot_rmaps(kvm, memslot, slot_rmap_write_protect,
6445 		kvm_tdp_mmu_wrprot_slot(kvm, memslot, start_level);
6681 				   const struct kvm_memory_slot *memslot,
6689 		kvm_shadow_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level);
6691 	kvm_tdp_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level, false);
6700 					const struct kvm_memory_slot *memslot,
6703 	u64 start = memslot->base_gfn;
6704 	u64 end = start + memslot->npages;
6711 		kvm_shadow_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level);
6716 	kvm_tdp_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level, true);
6723 	 * ioctl to enable dirty logging on this memslot completes. Since the
6796 				   const struct kvm_memory_slot *memslot)
6804 		walk_slot_rmaps_4k(kvm, memslot, __rmap_clear_dirty, false);
6810 		kvm_tdp_mmu_clear_dirty_slot(kvm, memslot);
7221 		 * other hand, if any memslot has logging enabled, chances are
7225 		 * If a memslot update is in progress, reading an incorrect value
7412 			 * by the memslot, KVM can't use a hugepage due to the
7434 		 * contained by the memslot.  Like the head page, KVM can't
7460 		 * entirely contained by the memslot.