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-ia64-devel

[Xen-ia64-devel] Re: [patch 00/12] Kexec: EFI Mapping: Take IV

To: Simon Horman <horms@xxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Re: [patch 00/12] Kexec: EFI Mapping: Take IV
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Thu, 06 Dec 2007 15:58:24 -0700
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, Aron Griffis <aron@xxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Dec 2007 14:58:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071206033156.GA13492@xxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: HP OSLO R&D
References: <20071127091913.832166139@xxxxxxxxxxxx> <1196897042.6509.53.camel@lappy> <20071206033156.GA13492@xxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Simon,

   So there's really nothing special to reproduce the SAL problem.  I
reproduced it first try on a zx2000.  I imagine any of the first
generation HP Itanium 2 boxes with latest firmware will hit it.  This
includes: rx2600, zx6000, and zx2000 with firmware 2.31.  I can set one
up if you can't find one.  I've only gone so far as to verify that the
sal_proc entry point does live in a runtime mapping, EFI
SetVirtualAddressMap returns success, and decoding the status returned
by the SAL calls.  The status is quite strange and makes me wonder what
code I'm jumping into; I get this: 0xe00000003f930000.  I got the same
value back for a few SAL calls.  I wish I had an ITP hooked up to a
system doing this so we could watch where it's going.  The problem only
shows up when the relocation is activated by the last kexec patch, so
it's not an intermediate patch inadvertently doing something extra.  Let
me know if you have any thoughts on how to debug this.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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

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