Searched refs:XSAVE (Results 1 – 10 of 10) sorted by relevance
| /Linux-v6.6/arch/x86/kernel/fpu/ |
| D | xstate.h | 81 #define XSAVE ".byte " REX_PREFIX "0x0f,0xae,0x27" macro
118 asm volatile(ALTERNATIVE_3(XSAVE, \
279 XSTATE_OP(XSAVE, buf, lmask, hmask, err); in xsave_to_user_sigframe()
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | xstate.rst | 21 must include an XSAVE buffer defined by the CPU.
24 because different CPUs have differently-sized XSAVE buffers. A compiled-in
144 configuration. Signal handlers can examine the XSAVE buffer's XSTATE_BV
|
| D | cpuinfo.rst | 149 missing at runtime. For example, AVX flags will not show up if XSAVE feature
150 is disabled since they depend on XSAVE feature. Another example would be broken
|
| D | sva.rst | 86 This MSR is managed with the XSAVE feature set as "supervisor state" to
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| D | gather_data_sampling.rst | 66 If used, these options will disable AVX use by turning off XSAVE YMM support.
68 does not follow proper AVX enumeration to check both AVX *and* XSAVE YMM
|
| /Linux-v6.6/tools/arch/x86/kcpuid/ |
| D | cpuid.csv | 45 1, 0, ECX, 26, xsave, XSAVE/XRSTOR processor extended states (XSETBV/XGETBV/XCR0)
74 1, 0, EDX, 24, fxsr, XSAVE and FXRSTOR Instrs
253 0xD, 0, ECX, 31:0, max_sz_xsave, Maximum size (bytes) of the XSAVE/XRSTOR save area
|
| /Linux-v6.6/arch/x86/kvm/ |
| D | cpuid.c | 606 0 /* Reserved*/ | F(AES) | F(XSAVE) | 0 /* OSXSAVE */ | F(AVX) | in kvm_set_cpu_caps()
|
| /Linux-v6.6/arch/x86/lib/ |
| D | x86-opcode-map.txt | 1129 4: XSAVE | ptwrite Ey (F3),(11B)
|
| /Linux-v6.6/tools/arch/x86/lib/ |
| D | x86-opcode-map.txt | 1129 4: XSAVE | ptwrite Ey (F3),(11B)
|
| /Linux-v6.6/arch/x86/kvm/vmx/ |
| D | vmx.c | 7670 cr4_fixed1_update(X86_CR4_OSXSAVE, ecx, feature_bit(XSAVE)); in nested_vmx_cr_fixed1_bits_update()
|
