Searched refs:vpid02 (Results 1 – 4 of 4) sorted by relevance
92 return vmx->nested.vpid02 ? vmx->nested.vpid02 : vmx->vpid; in nested_get_vpid02()
347 free_vpid(vmx->nested.vpid02); in free_nested() 1194 * If L1 uses VPID and we allocated a vpid02, TLB entries are tagged1196 * while L2 entries are tagged with vmx->nested.vpid02).1203 (nested_cpu_has_vpid(vmcs12) && to_vmx(vcpu)->nested.vpid02); in nested_has_guest_tlb_tag() 2342 * VPID=0. I.e. using vpid02 would be ok (so long as KVM emulates the in prepare_vmcs02_early_rare() 2349 if (nested_cpu_has_vpid(vmcs12) && vmx->nested.vpid02) in prepare_vmcs02_early_rare() 2350 vmcs_write16(VIRTUAL_PROCESSOR_ID, vmx->nested.vpid02); in prepare_vmcs02_early_rare() 5353 vmx->nested.vpid02 = allocate_vpid(); in enter_vmx_operation() 5982 u16 vpid02; in handle_invvpid() local 6021 * Always flush the effective vpid02, in handle_invvpid() [all...]
188 u16 vpid02; member
3179 vpid_sync_vcpu_single(vmx->nested.vpid02); in vmx_flush_tlb_all()