From: Ryan Harper <ryanh@us.ibm.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: numa=on broken
Date: Fri, 30 Mar 2007 13:48:42 -0500 [thread overview]
Message-ID: <20070330184842.GW28736@us.ibm.com> (raw)
In-Reply-To: <20070330184620.GV28736@us.ibm.com>
* Ryan Harper <ryanh@us.ibm.com> [2007-03-30 13:46]:
> * Ryan Harper <ryanh@us.ibm.com> [2007-03-30 13:36]:
> > * Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2007-03-30 13:17]:
> > >
> > >
> > >
> > > On 30/3/07 19:08, "Ryan Harper" <ryanh@us.ibm.com> wrote:
> > >
> > > >> So -- can we ensure that the node that owns low memory is node zero?
> > > >
> > > > AFAIK, that is the case, look at the SRAT table:
> > > >
> > > > (XEN) SRAT: Node 0 PXM 0 0-a0000
> > > > (XEN) SRAT: Node 0 PXM 0 0-e0000000
> > > > (XEN) SRAT: Node 1 PXM 1 100000000-200000000
> > >
> > > What if you move end_boot_allocator() to just before 'early_boot = 0' in
> > > arch/x86/setup.c?
> >
> > Giving that a shot.
>
> Didn't work, just pushes the bubble back to allocating the array for
> NODE0:
Ah, top of end_boot_allocator assings avail[0] to avail0. Looks like
there is some heap/avail initiliazation that needs to be done
seperately.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2007-03-30 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 17:34 numa=on broken Ryan Harper
2007-03-30 17:51 ` Keir Fraser
2007-03-30 18:08 ` Ryan Harper
2007-03-30 18:17 ` Keir Fraser
2007-03-30 18:20 ` Ryan Harper
2007-03-30 18:46 ` Ryan Harper
2007-03-30 18:48 ` Ryan Harper [this message]
2007-03-30 18:51 ` Keir Fraser
2007-03-30 18:55 ` Ryan Harper
2007-03-30 19:05 ` Keir Fraser
2007-03-30 19:39 ` Ryan Harper
2007-03-31 9:06 ` Keir Fraser
2007-04-01 5:20 ` Ryan Harper
2007-04-01 8:29 ` Keir Fraser
2007-04-01 13:46 ` Ryan Harper
2007-04-01 15:51 ` Keir Fraser
2007-04-01 18:53 ` Ryan Harper
2007-03-30 19:03 ` Ryan Harper
2007-03-30 18:06 ` 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=20070330184842.GW28736@us.ibm.com \
--to=ryanh@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.