From: Tejun Heo <tj@kernel.org>
To: Hans Rosenfeld <hans.rosenfeld@amd.com>
Cc: "Seidel, Conny" <Conny.Seidel@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 32bit NUMA and fakeNUMA broken for AMD CPUs
Date: Wed, 29 Jun 2011 15:03:49 +0200 [thread overview]
Message-ID: <20110629130349.GM3386@htj.dyndns.org> (raw)
In-Reply-To: <20110629125507.GQ478@escobedo.osrc.amd.com>
On Wed, Jun 29, 2011 at 02:55:08PM +0200, Hans Rosenfeld wrote:
> On Wed, Jun 29, 2011 at 08:34:09AM -0400, Tejun Heo wrote:
> > So, mminit_verify_page_links() detects it while the last 512MiB
> > highmem chunk of node 0 is being initialized and freaks out.
> >
> > We definitely need a safe guard to check NUMA node alignment and
> > disable NUMA if it requires finer granuality than supported by the
> > memory model. If you use DISCONTIGMEM, which has 64MiB granuality,
> > instead, it works, right?
>
> I had DISCONTIGMEM enabled in the kernel config, it does not work.
Hmmm? The following is the relevant part from your .config.
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ILLEGAL_POINTER_VALUE=0
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
And it selects SPARSEMEM via SPARSEMEM_MANUAL. You need to choose
DISCONTIGMEM_MANUAL in "Processor type and features" -> "Memory
Model".
Thanks.
--
tejun
next prev parent reply other threads:[~2011-06-29 13:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 15:41 Conny Seidel
2011-06-26 10:22 ` Tejun Heo
[not found] ` <20110626223807.47cef5c6.conny.seidel_amd.com@marah.osrc.amd.com>
2011-06-28 9:41 ` [PATCH tip:x86/urgent] x86-32, NUMA: Fix boot regression caused by NUMA init unification on highmem machines Tejun Heo
2011-06-28 12:35 ` Conny Seidel
2011-07-01 15:26 ` [tip:x86/urgent] " tip-bot for Tejun Heo
[not found] ` <20110628174613.GP478@escobedo.osrc.amd.com>
2011-06-29 9:44 ` 32bit NUMA and fakeNUMA broken for AMD CPUs Tejun Heo
2011-06-29 10:51 ` Tejun Heo
2011-06-29 12:34 ` Tejun Heo
2011-06-29 12:55 ` Hans Rosenfeld
2011-06-29 13:03 ` Tejun Heo [this message]
2011-06-29 16:15 ` Tejun Heo
2011-06-30 13:13 ` Hans Rosenfeld
2011-06-30 15:55 ` Tejun Heo
2011-06-30 16:32 ` Hans Rosenfeld
2011-06-30 16:42 ` Tejun Heo
2011-06-30 17:04 ` Hans Rosenfeld
2011-07-01 16:22 ` [PATCH x86/urgent 1/2] x86: s/PAGES_PER_ELEMENT/PAGES_PER_SECTION/ Tejun Heo
2011-07-01 16:23 ` [PATCH x86/urgent 2/2] x86: Implement pfn -> nid mapping granularity check Tejun Heo
2011-07-09 8:32 ` Tejun Heo
2011-07-09 8:42 ` H. Peter Anvin
2011-07-11 8:34 ` [PATCH x86/urgent] x86: Disable AMD_NUMA for 32bit for now Tejun Heo
2011-07-11 14:01 ` Tejun Heo
2011-07-11 18:58 ` [tip:x86/urgent] " tip-bot for Tejun Heo
2011-07-11 14:20 ` [PATCH x86/urgent 2/2] x86: Implement pfn -> nid mapping granularity check Hans Rosenfeld
2011-07-13 5:34 ` [tip:x86/numa] x86, numa: " tip-bot for Tejun Heo
2011-07-12 7:44 [PATCH x86/mm 1/2] x86: s/PAGES_PER_ELEMENT/PAGES_PER_SECTION/ Tejun Heo
2011-07-12 7:45 ` [PATCH x86/mm 2/2] x86: Implement pfn -> nid mapping granularity check Tejun Heo
2011-07-13 5:33 ` [tip:x86/numa] x86, mm: s/PAGES_PER_ELEMENT/PAGES_PER_SECTION/ tip-bot for Tejun Heo
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=20110629130349.GM3386@htj.dyndns.org \
--to=tj@kernel.org \
--cc=Conny.Seidel@amd.com \
--cc=hans.rosenfeld@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®