Lines Matching defs:memslot
1377 * of memslot has no such restriction, so the range can cross two large
1935 * differs then the memslot lookup (SMM vs. non-SMM) will be bogus, the
3088 * Note, using the already-retrieved memslot and __gfn_to_hva_memslot()
3093 * read-only memslot.
3742 * were made now versus when the memslot was created.
4260 * Retry the page fault if the gfn hit a memslot that is being deleted
4261 * or moved. This ensures any existing SPTEs for the old memslot will
4338 * root was invalidated by a memslot update or a relevant mmu_notifier fired.
5514 * (b) remote reloads due to a memslot update obsoletes _all_ roots
5518 * Note! Dummy roots are unique in that they are obsoleted by memslot
6109 * It's required when memslot is being deleted or VM is being
6155 * returning to the caller, e.g. if the zap is in response to a memslot
6157 * associated with the deleted memslot once the update completes, and
6206 const struct kvm_memory_slot *memslot;
6220 memslot = iter.slot;
6221 start = max(gfn_start, memslot->base_gfn);
6222 end = min(gfn_end, memslot->base_gfn + memslot->npages);
6226 flush = __walk_slot_rmaps(kvm, memslot, __kvm_zap_rmap,
6271 const struct kvm_memory_slot *memslot,
6276 walk_slot_rmaps(kvm, memslot, slot_rmap_write_protect,
6283 kvm_tdp_mmu_wrprot_slot(kvm, memslot, start_level);
6519 const struct kvm_memory_slot *memslot,
6527 kvm_shadow_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level);
6529 kvm_tdp_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level, false);
6538 const struct kvm_memory_slot *memslot,
6541 u64 start = memslot->base_gfn;
6542 u64 end = start + memslot->npages;
6549 kvm_shadow_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level);
6554 kvm_tdp_mmu_try_split_huge_pages(kvm, memslot, start, end, target_level, true);
6561 * ioctl to enable dirty logging on this memslot completes. Since the
6634 const struct kvm_memory_slot *memslot)
6642 walk_slot_rmaps_4k(kvm, memslot, __rmap_clear_dirty, false);
6648 kvm_tdp_mmu_clear_dirty_slot(kvm, memslot);
7059 * other hand, if any memslot has logging enabled, chances are
7063 * If a memslot update is in progress, reading an incorrect value