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

Re: [Xen-devel] Wrong number of sockets on IBM x3850 M2

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Wrong number of sockets on IBM x3850 M2
From: Gary Grebus <ggrebus@xxxxxxxxxxxxxxx>
Date: Thu, 07 May 2009 13:32:49 -0400
Delivery-date: Thu, 07 May 2009 10:33:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C628AFF8.A27F%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C628AFF8.A27F%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2009-05-07 at 15:34 +0100, Keir Fraser wrote:
> On 07/05/2009 15:06, "Gary Grebus" <ggrebus@xxxxxxxxxxxxxxx> wrote:
> 
> > One of our customers has reported that Xen determines the wrong topology
> > for their machines, identifying them as 6 sockets x 4 cores when in fact
> > they are 4 sockets x 6 cores (Intel(R) Xeon(R) CPU X7460  @ 2.66GHz
> > stepping 01).  The systems are IBM x3850 M2.
> 
> Where is this reported? Via the SYSCTL_physinfo hypercall? 

Right.

> You might have to
> work backwards from the cpu_sibling_map and cpu_core_map values which are
> used there to derive the info returned by that hypercall. The fact that the
> APIC IDs of the CPUs are pretty random and jumbled as the CPUs are brought
> up should not matter.
> 

cpu_sibling_map[] and cpu_core_map[] are built based on the
phys_proc_id[] and cpu_core_id[] arrays, which are set based on
phys_pkg_id(), which is what led me back to the APIC IDs.

I suspect the jumbled IDs come from the BIOS, and that CPUID might
report the real topology, but was hoping someone familiar with the
platform might confirm that.

  /gary 




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

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