Searched refs:disallow_lpage (Results 1 – 4 of 4) sorted by relevance
732 old = linfo->disallow_lpage; in update_gfn_disallow_lpage_count()733 linfo->disallow_lpage += count; in update_gfn_disallow_lpage_count()734 WARN_ON_ONCE((old ^ linfo->disallow_lpage) & KVM_LPAGE_MIXED_FLAG); in update_gfn_disallow_lpage_count()3269 if (!linfo->disallow_lpage) in __kvm_mmu_max_mapping_level()7676 return lpage_info_slot(gfn, slot, level)->disallow_lpage & KVM_LPAGE_MIXED_FLAG; in hugepage_test_mixed()7682 lpage_info_slot(gfn, slot, level)->disallow_lpage &= ~KVM_LPAGE_MIXED_FLAG; in hugepage_clear_mixed()7688 lpage_info_slot(gfn, slot, level)->disallow_lpage |= KVM_LPAGE_MIXED_FLAG; in hugepage_set_mixed()
459 To check the last two conditions, the mmu maintains a ->disallow_lpage set of461 causes its disallow_lpage to be incremented, thus preventing instantiation of
1074 int disallow_lpage; member
12990 linfo[0].disallow_lpage = 1; in kvm_alloc_memslot_metadata()12992 linfo[lpages - 1].disallow_lpage = 1; in kvm_alloc_memslot_metadata()13002 linfo[j].disallow_lpage = 1; in kvm_alloc_memslot_metadata()