Displaying 4 results from an estimated 4 matches for "xsave_enabled".
Did you mean:
xsaves_enabled
2011 May 18
1
Re: [PATCH] x86: clear CPUID output of leaf 0xd for Dom0 when xs
...n is that a future Intel revision may expand this function and return other information besides that XSAVEOPT, which would then be wiped out by the fall-through code. I''m thinking something like this. Let me know if I have misunderstood something.
+ case 0xd: /* XSAVE */
+ if (!xsave_enabled(current))
+ __clear_bit(X86_FEATURE_XSAVEOPT % 32, &a);
+ break;
case 5: /* MONITOR/MWAIT */
Roger R. Cruz
----------------------
Linux starting with 2.6.36 uses the XSAVEOPT instruction and has
certain code paths that look only at the feature bit reported through
CPUID...
2011 Nov 24
0
[PATCH 6/6] X86: implement PCID/INVPCID for hvm
...& X86_CR4_PCIDE) && (old_cr & X86_CR4_PCIDE)) )
+ {
if ( !nestedhvm_vmswitch_in_progress(v) && nestedhvm_vcpu_in_guestmode(v) )
paging_update_nestedmode(v);
else
@@ -2409,10 +2430,18 @@ void hvm_cpuid(unsigned int input, unsig
if ( xsave_enabled(v) )
*ecx |= (v->arch.hvm_vcpu.guest_cr[4] & X86_CR4_OSXSAVE) ?
cpufeat_mask(X86_FEATURE_OSXSAVE) : 0;
+
+ /* Not expose PCID to non-hap hvm */
+ if ( !hap_enabled(d) )
+ *ecx &= ~cpufeat_mask(X86_FEATURE_PCID);
break;...
2013 Sep 23
11
[PATCH v4 0/4] x86/HVM: miscellaneous improvements
The first and third patches are cleaned up versions of an earlier v3
submission by Yang.
1: Nested VMX: check VMX capability before read VMX related MSRs
2: VMX: clean up capability checks
3: Nested VMX: fix IA32_VMX_CR4_FIXED1 msr emulation
4: x86: make hvm_cpuid() tolerate NULL pointers
Signed-off-by: Jan Beulich <jbeulich@suse.com>
2013 Jun 04
12
[PATCH 0/4] XSA-52..54 follow-up
The first patch really isn''t as much of a follow-up than what triggered
the security issues to be noticed in the first place.
1: x86: preserve FPU selectors for 32-bit guest code
2: x86: fix XCR0 handling
3: x86/xsave: adjust state management
4: x86/fxsave: bring in line with recent xsave adjustments
The first two I would see as candidates for 4.3 (as well as
subsequent backporting,