Re: [Xen-devel] XSAVE/XRSTOR crash resurgence in 4.3

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 15.07.13 at 15:49, Ben Guthro <ben.guthro@xxxxxxxxx> wrote:
> The following output was from a WinXP SP3 guest (32bit) on a Lenovo T430:
> 
> (XEN) d1v0: fip=1b773d6e9a fdp=23773d1c48 w=8
> (XEN) d1v0: FIP=1b773d6e9a FDP=23773d1c48 w=8
> (XEN) d1v1: fip=1b79e78dee fdp=230012e3b4 w=8
> (XEN) d1v1: FIP=1b79e78dee FDP=230012e3b4 w=8
> (XEN) d1v1: fip=0000:79e78dee fdp=0000:0012e3b4
> (XEN) d1v1: fip=0000:79e78dee fdp=0000:0012e3b4
> (XEN) d1v1: fip=0000:79e78dee fdp=0000:0012e3b4
> (XEN) d1v1: fip=0000:79e78dee fdp=0000:0012e3b4
> (XEN) d1v1: fip=1b79e78dee fdp=230012d528 w=8
> (XEN) d1v1: FIP=1b79e78dee FDP=230012d528 w=8
> (XEN) d1v0: fip=4500000000 fdp=4b1000000000 w=8
> (XEN) d1v0: FIP=4500000000 FDP=4b1000000000 w=8
> (XEN) d1v1: fip=1b773d6e9a fdp=23773d1c48 w=8
> (XEN) d1v1: FIP=1b773d6e9a FDP=23773d1c48 w=8

Well, it should have been quite obvious (to me) that this is
related to xsaveopt behavior (according to my own observations
of cases where the selector/offset fields don't get written). Could
you double check whether the system(s) you see the problem on
support xsaveopt, and if so, simply comment out the conditionals
that cause it to be used?

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel