On fpu deactivation, the cr0 read shadow is not properly updated, since
it assumes vcpu->arch.cr0 contains the guest visible cr0 value before
guest had control of cr0.ts.
This is not true, since cr0 has been decached (from vmx_fpu_deactivate
itself or somewhere else).
Fix by unconditionally upda
On 02/01/2010 06:48 PM, Marcelo Tosatti wrote:
On fpu deactivation, the cr0 read shadow is not properly updated, since
it assumes vcpu->arch.cr0 contains the guest visible cr0 value before
guest had control of cr0.ts.
This is not true, since cr0 has been decached (from vmx_fpu_deactivate
itself
