From: Tim Deegan <Tim.Deegan@citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xm save + restore crashes Windows 200832-bit(4.0.2-rc2-pre) (AMD only)
Date: Tue, 25 Jan 2011 14:37:22 +0000 [thread overview]
Message-ID: <20110125143722.GF13241@whitby.uk.xensource.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01BB9283@trantor>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
At 13:35 +0000 on 25 Jan (1295962540), James Harper wrote:
> So the problem is somewhere past hvm_set_segment_register, and because
> it's amd only, probably in or beyond svm_set_segment_register. The first
> 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 syncing
of the vmcb in the save routine is not conditional on v == current, and
the "already synced" bit that it would otherwise gate on isn't properly
initialized.
Try the attached patch; I'm sorry to say that I suspect it will fix the
odd output of xen_hvmctx but probably won't fix the BSOD. :(
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
[-- Attachment #2: vmcb-sync --]
[-- Type: text/plain, Size: 353 bytes --]
diff -r 9b453f96dd46 xen/arch/x86/hvm/svm/vmcb.c
--- a/xen/arch/x86/hvm/svm/vmcb.c Fri Jan 21 16:03:04 2011 +0000
+++ b/xen/arch/x86/hvm/svm/vmcb.c Tue Jan 25 14:36:32 2011 +0000
@@ -280,6 +280,7 @@ int svm_create_vmcb(struct vcpu *v)
}
arch_svm->vmcb_pa = virt_to_maddr(arch_svm->vmcb);
+ arch_svm->vmcb_in_sync = 1;
return 0;
}
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-01-25 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 4:20 xm save + restore crashes Windows 2008 32-bit (4.0.2-rc2-pre) James Harper
2011-01-25 9:24 ` Tim Deegan
2011-01-25 9:28 ` James Harper
2011-01-25 10:39 ` Tim Deegan
2011-01-25 10:43 ` James Harper
2011-01-25 10:53 ` Tim Deegan
2011-01-25 11:01 ` James Harper
2011-01-25 11:12 ` Tim Deegan
2011-01-25 11:24 ` James Harper
2011-01-25 11:37 ` James Harper
2011-01-25 11:52 ` xm save + restore crashes Windows 2008 32-bit(4.0.2-rc2-pre) James Harper
2011-01-25 13:35 ` xm save + restore crashes Windows 200832-bit(4.0.2-rc2-pre) (AMD only) James Harper
2011-01-25 14:37 ` Tim Deegan [this message]
2011-01-25 22:11 ` James Harper
2011-01-25 22:21 ` Tim Deegan
2011-01-25 22:25 ` James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110125143722.GF13241@whitby.uk.xensource.com \
--to=tim.deegan@citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.