Re: [Xen-devel] [PATCH for-4.11 v2 1/3] x86/HVM: don't cause #NM to be raised in Xen

2018-07-01 Thread Tian, Kevin
> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Tuesday, June 26, 2018 2:36 PM > > 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 > wr

Re: [Xen-devel] [PATCH for-4.11 v2 1/3] x86/HVM: don't cause #NM to be raised in Xen

2018-06-26 Thread Andrew Cooper
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. >

[Xen-devel] [PATCH for-4.11 v2 1/3] x86/HVM: don't cause #NM to be raised in Xen

2018-06-25 Thread Jan Beulich
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_inter