Home
last modified time | relevance | path

Searched refs:XSAVES (Results 1 - 11 of 11) sorted by relevance

/kernel/linux/linux-6.6/arch/x86/kvm/
H A Dgoverned_features.h9 KVM_GOVERNED_X86_FEATURE(XSAVES)
H A Dcpuid.c686 F(XSAVEOPT) | F(XSAVEC) | F(XGETBV1) | F(XSAVES) | f_xfd in kvm_set_cpu_caps()
1042 if (entry->eax & (F(XSAVES)|F(XSAVEC))) in __do_cpuid_func()
/kernel/linux/linux-6.6/arch/x86/kernel/fpu/
H A Dxstate.h84 #define XSAVES ".byte " REX_PREFIX "0x0f,0xc7,0x2f" macro
102 * If XSAVES is enabled, it replaces XSAVEC because it supports supervisor
121 XSAVES, X86_FEATURE_XSAVES) \
175 * Uses either XSAVE or XSAVEOPT or XSAVES depending on the CPU features
197 * Uses XRSTORS when XSAVES is used, XRSTOR otherwise.
H A Dxstate.c194 * MSR_IA32_XSS sets supervisor states managed by XSAVES. in fpu__init_cpu_xstate()
593 * XSAVES. in paranoid_xstate_size_valid()
596 XSTATE_WARN_ON(1, "Got supervisor feature %d, but XSAVES not advertised\n", i); in paranoid_xstate_size_valid()
611 * that we use 'XSAVES' on, we could potentially overflow the
612 * buffer because 'XSAVES' saves system states too.
623 * the XSAVES instruction for an XSAVE area in get_compacted_size()
628 * When XSAVES is not available but XSAVEC is (virt), then there in get_compacted_size()
657 /* Re-enable independent features so XSAVES will work on them again. */ in get_xsave_compacted_size()
687 * XSAVES kernel size includes supervisor states and uses compacted in init_xstate_size()
913 * of XSAVES an in fpu__resume_cpu()
[all...]
/kernel/linux/linux-5.10/arch/x86/include/asm/fpu/
H A Dinternal.h219 #define XSAVES ".byte " REX_PREFIX "0x0f,0xc7,0x2f" macro
241 * If XSAVES is enabled, it replaces XSAVEOPT because it supports a compact
257 XSAVES, X86_FEATURE_XSAVES) \
/kernel/linux/linux-5.10/arch/x86/kernel/fpu/
H A Dxstate.c236 * MSR_IA32_XSS sets supervisor states managed by XSAVES. in fpu__init_cpu_xstate()
402 * Setup offsets of a supervisor-state-only XSAVES buffer:
494 * works with XSAVE, but not with XSAVEOPT and XSAVES because in setup_init_fpu_buf()
499 * data when XSAVES is available because XSAVES uses xstate in setup_init_fpu_buf()
515 * Only XSAVES supports supervisor states and it uses compacted in xfeature_uncompacted_offset()
539 * 'XSAVES' implies two different things:
544 * that it is obvious which aspect of 'XSAVES' is being handled
670 * XSAVES, which is compacted-format only. in do_extra_xstate_size_checks()
701 * that we use 'XSAVES' o
[all...]
/kernel/linux/linux-5.10/arch/x86/include/asm/
H A Dvmx.h71 #define SECONDARY_EXEC_XSAVES VMCS_CONTROL_BIT(XSAVES)
/kernel/linux/linux-5.10/tools/lib/traceevent/plugins/
H A Dplugin_kvm.c115 _ER(XSAVES, 63) \
/kernel/linux/linux-6.6/arch/x86/include/asm/
H A Dvmx.h74 #define SECONDARY_EXEC_ENABLE_XSAVES VMCS_CONTROL_BIT(XSAVES)
/kernel/linux/linux-5.10/arch/x86/kvm/
H A Dcpuid.c440 F(XSAVEOPT) | F(XSAVEC) | F(XGETBV1) | F(XSAVES) in kvm_set_cpu_caps()
731 if (entry->eax & (F(XSAVES)|F(XSAVEC))) in __do_cpuid_func()
/kernel/linux/linux-6.6/arch/x86/kvm/vmx/
H A Dvmx.c4644 vmx_adjust_sec_exec_feature(vmx, &exec_control, xsaves, XSAVES); in vmx_secondary_exec_control()
7769 * XSAVES is effectively enabled if and only if XSAVE is also exposed in vmx_vcpu_after_set_cpuid()
7770 * to the guest. XSAVES depends on CR4.OSXSAVE, and CR4.OSXSAVE can be in vmx_vcpu_after_set_cpuid()

Completed in 22 milliseconds