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

Re: [Xen-ia64-devel] Re: [patch] emulate more SN2 SAL calls

To: Jes Sorensen <jes@xxxxxxx>
Subject: Re: [Xen-ia64-devel] Re: [patch] emulate more SN2 SAL calls
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Thu, 24 May 2007 14:10:58 -0600
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 24 May 2007 13:09:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4653E330.5020201@xxxxxxx>
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: <4652EB83.3030400@xxxxxxx> <1179862282.6432.10.camel@lappy> <4653E330.5020201@xxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2007-05-23 at 08:46 +0200, Jes Sorensen wrote:
> Alex Williamson wrote:
> > On Tue, 2007-05-22 at 15:09 +0200, Jes Sorensen wrote:
> >> Hi,
> >>
> >> We need some more SAL calls emulated on SN2.
> > 
> >    Are we getting to a point that we should should expand the machine
> > vectors when running on Xen to include a platform specific SAL emulator?
> > For example, ia64_mv.oem_sal_emulator?  Thanks,
> 
> Hi Alex,
> 
> I'd prefer to just keep them in the global file and it's slow path code
> so it's not a big issue. Kinda like ioctls. In addition, we may one day
> want to emulate an Altix on a ZX1 or vice versa :-)

  Ok, I can live with it for now.  Isn't there also a chance that
vendors could have overlapping OEM SAL calls, or did SGI get assigned
0x020000XX?  In practice, I don't think this is a problem, but making it
part of the machine vector would eliminate that chance.  One other nit,
there's a stray printk("."); in SN_SAL_IOIF_GET_DEVICE_DMAFLUSH_LIST.
Was that supposed to be in the #ifdef'd out code?  It might be nice to
use loglevels for these printks so you can see them w/o changing code.
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>