Searched refs:XSAVES (Results 1 – 5 of 5) sorted by relevance
/linux/arch/x86/include/asm/ |
H A D | vmx.h | 76 #define SECONDARY_EXEC_ENABLE_XSAVES VMCS_CONTROL_BIT(XSAVES)
|
/linux/arch/x86/kvm/ |
H A D | cpuid.c | 1010 F(XSAVES), in kvm_set_cpu_caps() 1478 if (entry->eax & (feature_bit(XSAVES) | feature_bit(XSAVEC))) in __do_cpuid_func()
|
/linux/arch/x86/kernel/fpu/ |
H A D | xstate.c | 1449 XSTATE_OP(XSAVES, xstate, (u32)mask, (u32)(mask >> 32), err); in xsaves()
|
/linux/tools/arch/x86/kcpuid/ |
H A D | cpuid.csv | 359 0xd, 1, eax, 3, xsaves , XSAVES/XRSTORS instructions (and XSS MSR)
|
/linux/arch/x86/kvm/vmx/ |
H A D | vmx.c | 4544 vmx_adjust_sec_exec_feature(vmx, &exec_control, xsaves, XSAVES); in vmx_secondary_exec_control() 7725 * XSAVES is effectively enabled if and only if XSAVE is also exposed in vmx_vcpu_after_set_cpuid() 7726 * to the guest. XSAVES depends on CR4.OSXSAVE, and CR4.OSXSAVE can be in vmx_vcpu_after_set_cpuid()
|