All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: "Subrahmanian, Raj" <raj.subrahmanian@unisys.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Numa=on broken?
Date: Fri, 4 May 2007 08:33:14 -0500	[thread overview]
Message-ID: <20070504133314.GR27552@us.ibm.com> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F605025EC7@USTR-EXCH5.na.uis.unisys.com>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

* Subrahmanian, Raj <raj.subrahmanian@unisys.com> [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.

I'd also be interested in your SRAT table output for this machine.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

[-- Attachment #2: numa_debug.patch --]
[-- Type: text/plain, Size: 910 bytes --]

diff -r 3a5722420de7 xen/common/page_alloc.c
--- a/xen/common/page_alloc.c	Thu May 03 19:25:47 2007 +0100
+++ b/xen/common/page_alloc.c	Fri May 04 08:29:48 2007 -0500
@@ -353,6 +353,8 @@ static struct page_info *alloc_heap_page
     ASSERT(zone_lo <= zone_hi);
     ASSERT(zone_hi < NR_ZONES);
 
+    printk("%s: request for node %d\n", node);
+
     if ( unlikely(order > MAX_ORDER) )
         return NULL;
 
@@ -543,8 +545,10 @@ void init_heap_pages(
 
         if ( !avail[nid_curr] )
         {
+            printk("%s: attempting to initialize avail[%d]\n", nid_curr);
             avail[nid_curr] = xmalloc_array(unsigned long, NR_ZONES);
             memset(avail[nid_curr], 0, NR_ZONES * sizeof(long));
+            printk("%s: attempting to initialize _heap[%d]\n", nid_curr);
             _heap[nid_curr] = xmalloc(heap_by_zone_and_order_t);
             init_heap_block(_heap[nid_curr]);
         }

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2007-05-04 13:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B05D2E415E8CC94897BB44233D14EE6805A01ED6@USTR-EXCH5.na.uis.unisys.com>
2007-05-03 19:25 ` Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments) Krysan, Susan
2007-05-03 20:29   ` Keir Fraser
2007-05-03 22:29     ` Numa=on broken? Subrahmanian, Raj
2007-05-03 23:10       ` Ryan Harper
2007-05-04  2:39         ` Subrahmanian, Raj
2007-05-04  6:23         ` Subrahmanian, Raj
2007-05-04 13:33           ` Ryan Harper [this message]
2007-05-04 13:38             ` Ryan Harper
2007-05-04 17:32               ` Subrahmanian, Raj
2007-05-07 20:24               ` Subrahmanian, Raj
2007-05-07 20:43                 ` Ryan Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070504133314.GR27552@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=raj.subrahmanian@unisys.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.