On 26/06/18 07:36, Jan Beulich wrote:
> The changes for XSA-267 did not touch management of CR0.TS for HVM
> guests. In fully eager mode this bit should never be set when
> respective vCPU-s are active, or else hvmemul_get_fpu() might leave it
> wrongly set, leading to #NM in hypervisor context.
>
> {svm,vmx}_enter() and {svm,vmx}_fpu_dirty_intercept() become unreachable
> this way. Explicit {svm,vmx}_fpu_leave() invocations need to be guarded
> now.
>
> With no CR0.TS management necessary in fully eager mode, there's also no
> need anymore to intercept #NM.
>
> Reported-by: Charles Arnold <[email protected]>
> Signed-off-by: Jan Beulich <[email protected]>Reviewed-by: Andrew Cooper <[email protected]> _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
