This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] xm save + restore crashes Windows 200832-bit(4.0.2-rc2-p

To: "Tim Deegan" <Tim.Deegan@xxxxxxxxxx>
Subject: RE: [Xen-devel] xm save + restore crashes Windows 200832-bit(4.0.2-rc2-pre) (AMD only)
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Wed, 26 Jan 2011 09:11:27 +1100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 25 Jan 2011 14:13:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110125143722.GF13241@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01BB9269@trantor> <20110125092440.GA13241@xxxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB927B@trantor> <20110125103938.GB13241@xxxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB927D@trantor> <20110125105313.GC13241@xxxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB9280@trantor> <AEC6C66638C05B468B556EA548C1A77D01BB9282@trantor> <AEC6C66638C05B468B556EA548C1A77D01BB9283@trantor> <20110125143722.GF13241@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acu8nWgdwEkniVKoR7Gpfnth5lffswAPmRtQ
Thread-topic: [Xen-devel] xm save + restore crashes Windows 200832-bit(4.0.2-rc2-pre) (AMD only)
> At 13:35 +0000 on 25 Jan (1295962540), James Harper wrote:
> > So the problem is somewhere past hvm_set_segment_register, and
> > it's amd only, probably in or beyond svm_set_segment_register. The
> > thing I notice in that routine is that there is a case for those 4
> > registers... although all it seems to do is svm_sync_vmcb before and
> > svm_vmload after setting. I don't know what those two do though.
> Hmm; I suspect the bug here is actually in the save side -- the
> of the vmcb in the save routine is not conditional on v == current,
> the "already synced" bit that it would otherwise gate on isn't
> initialized.
> Try the attached patch; I'm sorry to say that I suspect it will fix
> odd output of xen_hvmctx but probably won't fix the BSOD. :(

Just to clarify, in the restore path I print the values to be saved to
the segment registers, then I read the segment registers and print the
values that are in them. They aren't the same. Doesn't that sound like a
problem on the restore side?


Xen-devel mailing list