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


RE: [Xen-devel] Numa=on broken?

To: "Ryan Harper" <ryanh@xxxxxxxxxx>
Subject: RE: [Xen-devel] Numa=on broken?
From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date: Fri, 4 May 2007 13:32:27 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 May 2007 10:31:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070504133821.GS27552@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceOUYaTL4qARXEiTLqCOriK1l/m4wAIHN8Q
Thread-topic: [Xen-devel] Numa=on broken?
I will try this out once I get the machine.
Incidentally, it seems to work with numa=on on a single-node machine.

>-----Original Message-----
>From: Ryan Harper [mailto:ryanh@xxxxxxxxxx] 
>Sent: Friday, May 04, 2007 9:38 AM
>To: Ryan Harper
>Cc: Subrahmanian, Raj; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Numa=on broken?
>* Ryan Harper <ryanh@xxxxxxxxxx> [2007-05-04 08:34]:
>> * Subrahmanian, Raj <raj.subrahmanian@xxxxxxxxxx> [2007-05-04 01:23]:
>> > Ryan,
>> > I did check out the mail discussion where you encountered 
>and fixed 
>> > this.
>> > I am seeing this again on 15009, unstable and in 15021 3.1. rc7.
>> > I have included the debug messages in both runs.
>> Hrm, well, we need to see which node the request is failing in so we 
>> can figure out how to initialize the heap.  I'm attaching a 
>patch that 
>> should hopefully dump out which node the memory request is 
>failing in.
>> Last time, it was the xmalloc() in xen/common/page_alloc.c in 
>> init_heap_pages().
>> Give this patch a spin and email me the output.
>Here is one that actually compiles.
>Ryan Harper
>Software Engineer; Linux Technology Center IBM Corp., Austin, Tx
>(512) 838-9253   T/L: 678-9253

Xen-devel mailing list