Re: [Xen-devel] XSAVE flavors

2016-02-17 Thread Shuai Ruan
On Thu, Feb 04, 2016 at 01:51:34AM -0700, Jan Beulich wrote: > >> >> And I'm afraid there's yet one more issue: If my reading of the > >> >> SDM is right, then the offsets at which components get saved > >> >> by XSAVEC / XSAVES aren't fixed, but depend on RFBM (as that's > >> >> what gets stored i

Re: [Xen-devel] XSAVE flavors

2016-02-04 Thread Jan Beulich
>>> On 04.02.16 at 07:49, wrote: > On Tue, Feb 02, 2016 at 02:42:38AM -0700, Jan Beulich wrote: >> >> > With this another question then is whether, when both XSAVEC >> >> > and XSAVEOPT are available, it is indeed always better to use >> >> > XSAVEC (as the code is doing after your enabling). >> >

Re: [Xen-devel] XSAVE flavors

2016-02-03 Thread Shuai Ruan
On Tue, Feb 02, 2016 at 02:42:38AM -0700, Jan Beulich wrote: > >> > With this another question then is whether, when both XSAVEC > >> > and XSAVEOPT are available, it is indeed always better to use > >> > XSAVEC (as the code is doing after your enabling). > > Yes. > > But current no machine only su

Re: [Xen-devel] XSAVE flavors

2016-02-02 Thread Jan Beulich
>>> On 02.02.16 at 07:31, wrote: > On Tue, Jan 26, 2016 at 08:12:20AM -0700, Jan Beulich wrote: >> >>> On 26.01.16 at 15:33, wrote: >> > originally I only meant to inquire about the state of the promised >> > alternatives improvement to the XSAVE code. However, while >> > looking over the code in

Re: [Xen-devel] XSAVE flavors

2016-02-01 Thread Shuai Ruan
On Tue, Jan 26, 2016 at 08:12:20AM -0700, Jan Beulich wrote: > >>> On 26.01.16 at 15:33, wrote: > > originally I only meant to inquire about the state of the promised > > alternatives improvement to the XSAVE code. However, while > > looking over the code in question again I stumbled across a > >

Re: [Xen-devel] XSAVE flavors

2016-01-26 Thread Jan Beulich
>>> On 26.01.16 at 15:33, wrote: > originally I only meant to inquire about the state of the promised > alternatives improvement to the XSAVE code. However, while > looking over the code in question again I stumbled across a > separate issue: XSAVES, just like XSAVEOPT, may use the > "modified" op

[Xen-devel] XSAVE flavors

2016-01-26 Thread Jan Beulich
Shuai, originally I only meant to inquire about the state of the promised alternatives improvement to the XSAVE code. However, while looking over the code in question again I stumbled across a separate issue: XSAVES, just like XSAVEOPT, may use the "modified" optimization. However, the fcs and fds