[Xen-changelog] [xen-unstable] Remove Xen workaround for HVM builder now that it's fixed

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
# Date 1172747329 0
# Node ID 3fb02f56c19f096edc6e3b23025389c84b41ec5d
# Parent  8939727a9d93b625b405c9e5391db562a4083ca0
Remove Xen workaround for HVM builder now that it's fixed
Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
---
 xen/arch/x86/domain.c |    9 +++------
 1 files changed, 3 insertions(+), 6 deletions(-)

diff -r 8939727a9d93 -r 3fb02f56c19f xen/arch/x86/domain.c
--- a/xen/arch/x86/domain.c     Thu Mar 01 11:04:45 2007 +0000
+++ b/xen/arch/x86/domain.c     Thu Mar 01 11:08:49 2007 +0000
@@ -501,12 +501,9 @@ int arch_set_info_guest(
     unsigned long flags;
     int i, rc = 0, compat;
 
-    /*
-     * HVM domain builder always builds caller-bitsize vcpu context.
-     * The PV builder is smarter and builds the appropriate type of context for
-     * the target domain. So the compat check here differs in the two cases.
-     */
-    compat = is_hvm_domain(d) ? IS_COMPAT(current->domain) : IS_COMPAT(d);
+    /* The context is a compat-mode one if the target domain is compat-mode;
+     * we expect the tools to DTRT even in compat-mode callers. */
+    compat = IS_COMPAT(d);
 
 #ifdef CONFIG_COMPAT
 #define c(fld) (compat ? (c.cmp->fld) : (c.nat->fld))

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog