From: tip-bot for Tejun Heo <tj@kernel.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hans.rosenfeld@amd.com,
hpa@zytor.com, mingo@redhat.com, conny.seidel@amd.com,
tj@kernel.org, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/urgent] x86: Disable AMD_NUMA for 32bit for now
Date: Mon, 11 Jul 2011 18:58:02 GMT [thread overview]
Message-ID: <tip-5da0ef9a8554a8d03dc880a53f213289fe7b576d@git.kernel.org> (raw)
In-Reply-To: <20110711083432.GC943@htj.dyndns.org>
Commit-ID: 5da0ef9a8554a8d03dc880a53f213289fe7b576d
Gitweb: http://git.kernel.org/tip/5da0ef9a8554a8d03dc880a53f213289fe7b576d
Author: Tejun Heo <tj@kernel.org>
AuthorDate: Mon, 11 Jul 2011 10:34:32 +0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 11 Jul 2011 16:25:30 +0200
x86: Disable AMD_NUMA for 32bit for now
Commit 2706a0bf7b ("x86, NUMA: Enable CONFIG_AMD_NUMA on 32bit
too") enabled AMD NUMA for 32bit too. Unfortunately, SPARSEMEM
on 32bit had rather coarse (512MiB) addr->node mapping
granularity due to lack of space in page->flags. This led to
boot failure on certain AMD NUMA machines which had 128MiB
alignment on nodes.
Patches to properly detect this condition and reject NUMA
configuration are posted[1] but deemed too pervasive for merge
at this point (-rc6). Disable AMD NUMA for 32bit for now and
re-enable once the detection logic is merged.
[1] http://thread.gmane.org/gmane.linux.kernel/1161279/focus=1162583
Reported-by: Hans Rosenfeld <hans.rosenfeld@amd.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Conny Seidel <conny.seidel@amd.com>
Link: http://lkml.kernel.org/r/20110711083432.GC943@htj.dyndns.org
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index da34972..37357a5 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1170,7 +1170,7 @@ comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
config AMD_NUMA
def_bool y
prompt "Old style AMD Opteron NUMA detection"
- depends on NUMA && PCI
+ depends on X86_64 && NUMA && PCI
---help---
Enable AMD NUMA node topology detection. You should say Y here if
you have a multi processor AMD system. This uses an old method to
next prev parent reply other threads:[~2011-07-11 18:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 15:41 32bit NUMA and fakeNUMA broken for AMD CPUs 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
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-bot for Tejun Heo [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=tip-5da0ef9a8554a8d03dc880a53f213289fe7b576d@git.kernel.org \
--to=tj@kernel.org \
--cc=conny.seidel@amd.com \
--cc=hans.rosenfeld@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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