WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] 64-bit failsafe callback

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] 64-bit failsafe callback
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 27 Mar 2006 23:57:59 +0200
Delivery-date: Mon, 27 Mar 2006 21:59:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
We're, while porting the kernel code back to SLES9, running into a case where 
the
failsafe callback gets entered. Looking at that code we don't seem to be able to
understand how it is actually expected to work. That code, out of load_segments,
stores the selectors (including one or more that failed) into the (extended) 
frame
for the kernel to pick them up. The kernel code, however, simply re-does the 
load
of these selectors - how can that be expected to work any better than in the
hypervisor? Further, the kernel blindly loads fs and gs, without caring to 
destroy
their base addresses and, even more importantly, its own ability to access the 
PDA.

Any clarification would be greatly appreciated.

Jan

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

<Prev in Thread] Current Thread [Next in Thread>