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


[Xen-devel] Re: c/s 21118: Magny-Coure breakage

To: Christoph Egger <Christoph.Egger@xxxxxxx>, Nitin A Kamble <nitin.a.kamble@xxxxxxxxx>
Subject: [Xen-devel] Re: c/s 21118: Magny-Coure breakage
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 12 Apr 2010 11:41:35 +0100
Cc: Andre Przywara <andre.przywara@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 12 Apr 2010 03:42:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201004121207.25060.Christoph.Egger@xxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcraKAbqqVIywAzWQwaTwtdeciMn2wABLIKi
Thread-topic: c/s 21118: Magny-Coure breakage
User-agent: Microsoft-Entourage/
We're at an intermediate state in 4.1 NUMA implementation I would say. That
changeset can be revised as necessary in future patches, but I think it is
broadly correct in that it's adding the right kind of extra things to the
control interfaces. Since we have 6-9 months before 4.1 is released we don't
need panic about regressions just yet.

 -- Keir

On 12/04/2010 11:07, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:

> Hi!
> Changeset 21118 breaks NUMA on AMD Magny-Coure due to introduction of
> 'sockets_per_node'. On AMD Magny-Coure we have two nodes on one socket, hence
> the existence of that field member introduces a breake on design level.
> Please revert changeset 21118 or rework the patch to get rid of this field
> member.
> Christoph

Xen-devel mailing list