All of lore.kernel.org
 help / color / mirror / Atom feed
From: beth kon <eak@us.ibm.com>
To: Xen-devel@lists.xensource.com
Subject: Problem with nr_nodes on large memory NUMA machine
Date: Fri, 19 Oct 2007 11:02:05 -0400	[thread overview]
Message-ID: <4718C6ED.6030504@us.ibm.com> (raw)

We've run into an issue with an 8 node x3950 where xm info is showing 
only 6 nodes. I've traced the problem to the clip_to_limit function in 
arch/x86/e820.c.

#ifdef __x86_64__
   clip_to_limit((uint64_t)(MACH2PHYS_COMPAT_VIRT_END -
                            __HYPERVISOR_COMPAT_VIRT_START) << 10,
                 "Only the first %u GB of the physical memory map "
                 "can be accessed by 32-on-64 guests.");
#endif

Boot messages....
(XEN) WARNING: Only the first 166 GB of the physical memory map can be 
accessed by 32-on-64 guests. (XEN) Truncating memory map to 174063616kB

After the memory is clipped, acpi_scan_nodes runs cutoff_node, which 
limits the memory associated with each node according to the cutoff 
values. Then, acpi_scan_nodes calls unparse_node to "remove" nodes that 
don't have the minimum amount of memory, due to the clipping of the 
memory range.

Can someone explain what this is all about and why it might be necessary?

-- 
Elizabeth Kon (Beth)
IBM Linux Technology Center
Open Hypervisor Team
email: eak@us.ibm.com

             reply	other threads:[~2007-10-19 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 15:02 beth kon [this message]
2007-10-19 15:14 ` Problem with nr_nodes on large memory NUMA machine Keir Fraser
2007-10-19 15:21   ` Subrahmanian, Raj
2007-10-19 15:32     ` Keir Fraser

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=4718C6ED.6030504@us.ibm.com \
    --to=eak@us.ibm.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.