[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Ryan Harper" <ryanh@xxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceOUYaTL4qARXEiTLqCOriK1l/m4wAIHN8Q
  • Thread-topic: [Xen-devel] Numa=on broken?

Ryan
I will try this out once I get the machine.
Incidentally, it seems to work with numa=on on a single-node machine.
Raj 

>-----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
>ryanh@xxxxxxxxxx
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.