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][Patch]Add two PAL calls which fix SMP windows insta

To: "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel][Patch]Add two PAL calls which fix SMP windows installation crashing bug
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Tue, 27 Mar 2007 10:43:16 -0600
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Mar 2007 09:42:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <58A36151585E4047913F40517D307BAE31AC3B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <58A36151585E4047913F40517D307BAE31AC3B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2007-03-27 at 09:18 +0800, Zhang, Xing Z wrote:
> Add two PAL calls -- PAL_LOGICAL_TO_PHYSICAL and PAL_FIXED_ADDR.
> 
> These PAL calls are invoked by SMP windows installation code.
> 
> The patch fix SMP windows installation crashing bug.

   This seems incomplete.  Doesn't a PAL_LOGICAL_TO_PHYSICAL
implementation imply we also need a working SAL_PHYSICAL_ID_INFO?  I
also get error messages about unimplemented PAL call #43
(PAL_CACHE_SHARED_INFO) when I try this.  According to the spec, this
call is required for any system reporting more than one logical
processor on a physical processor package.

   I think we should implement these calls, but why would we represent a
vCPU as anything more than a single processor per socket?  If we pretend
everything is a dual core processor with threads disabled, we get into
issues of reporting the correct socket number and thread number.  It
feels like it's just adding complication for no benefit.  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