Searched refs:GUEST_CR3 (Results 1 - 10 of 10) sorted by relevance
| /linux-master/tools/testing/selftests/kvm/x86_64/ |
| H A D | vmx_tsc_adjust_test.c | 98 save_cr3 = vmreadz(GUEST_CR3);
99 vmwrite(GUEST_CR3, -1ull);
104 vmwrite(GUEST_CR3, save_cr3);
|
| /linux-master/arch/x86/kvm/vmx/ |
| H A D | vmcs_shadow_fields.h | 65 SHADOW_FIELD_RW(GUEST_CR3, guest_cr3)
|
| H A D | vmcs12.c | 123 FIELD(GUEST_CR3, guest_cr3),
|
| H A D | hyperv_evmcs.c | 103 EVMCS1_FIELD(GUEST_CR3, guest_cr3,
|
| H A D | nested.c | 2669 * Immediately write vmcs02.GUEST_CR3. It will be propagated to vmcs12
2676 vmcs_writel(GUEST_CR3, vmcs12->guest_cr3);
3468 * Overwrite vmcs01.GUEST_CR3 with L1's CR3 if EPT is disabled *and*
3472 * GUEST_CR3 holds KVM's shadow CR3, not L1's "real" CR3, which causes
3474 * vmcs01.GUEST_CR3 results in the unwind naturally setting arch.cr3 to
3475 * the correct value. Smashing vmcs01.GUEST_CR3 is safe because nested
3476 * VM-Exits, and the unwind, reset KVM's MMU, i.e. vmcs01.GUEST_CR3 is
3478 * L1. Don't stuff vmcs01.GUEST_CR3 when using nested early checks as
3481 * path would need to manually save/restore vmcs01.GUEST_CR3.
3484 vmcs_writel(GUEST_CR3, vcp
[all...] |
| H A D | vmx.c | 2490 vcpu->arch.cr3 = vmcs_readl(GUEST_CR3);
3310 * (correctly) stop reading vmcs.GUEST_CR3 because it thinks
3348 * GUEST_CR3 is still vmx->ept_identity_map_addr if EPT + !URG.
3397 else /* vmcs.GUEST_CR3 is already up-to-date. */
3406 vmcs_writel(GUEST_CR3, guest_cr3);
6284 pr_err("CR3 = 0x%016lx\n", vmcs_readl(GUEST_CR3));
|
| /linux-master/tools/testing/selftests/kvm/include/x86_64/ |
| H A D | vmx.h | 256 GUEST_CR3 = 0x00006802, enumerator in enum:vmcs_field
|
| H A D | evmcs.h | 408 case GUEST_CR3:
849 case GUEST_CR3:
|
| /linux-master/tools/testing/selftests/kvm/lib/x86_64/ |
| H A D | vmx.c | 339 vmwrite(GUEST_CR3, vmreadz(HOST_CR3));
|
| /linux-master/arch/x86/include/asm/ |
| H A D | vmx.h | 330 GUEST_CR3 = 0x00006802, enumerator in enum:vmcs_field
|
Completed in 176 milliseconds