From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
fengguang.wu@intel.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [origin tree build failure] Re: [PULL] Please pull hwpoison code for 2.6.32
Date: Sat, 26 Sep 2009 20:11:34 +0200 [thread overview]
Message-ID: <20090926181134.GT30185@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0909260930410.3303@localhost.localdomain>
On Sat, Sep 26, 2009 at 09:35:07AM -0700, Linus Torvalds wrote:
>
>
> On Sat, 26 Sep 2009, Andi Kleen wrote:
> >
> > Thanks for the report. The issue comes from NODES_SHIFT=4
> >
> > I think I tested the NUMA case, but perhaps not with full NODES_SHIFT.
> >
> > The easy fix would be to limit NODES_SHIFT to 3 for 32bit (8 nodes max). Do you
> > have any problems with that? I doubt there are any >8 nodes NUMAQs left.
> > (last time I heard the last machine at IBM was down to < 4)
>
> No, just say "we don't support HWPOISON on 32-bit NUMA".
>
> Maybe simply using something like this.
That's a reasonable solution, but I would prefer to do it the other way round
(MEMORY_FAILURE disabling NUMA) to minimize user confusion. Also it's not
enough to just do NUMAQ, but needs all of 32bit NUMA, otherwise the NODES_SHIFT
could be set too high again.
Here's a compile tested patch (don't have a NUMAQ) implementing this:
---
x86: Don't allow 32bit NUMA together with hwpoison to avoid page flags overflow
From: Andi Kleen <ak@linux.intel.com>
Otherwise the enlarged sparsemem field in page->flags overflows 32bit,
which breaks compilation.
Reported by Ingo Molnar.
Originally based on a patch from Linus.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 9369879..384a897 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -423,6 +423,7 @@ config X86_32_NON_STANDARD
config X86_NUMAQ
bool "NUMAQ (IBM/Sequent)"
depends on X86_32_NON_STANDARD
+ depends on !MEMORY_FAILURE
select NUMA
select X86_MPPARSE
---help---
@@ -1108,6 +1109,7 @@ config NUMA
bool "Numa Memory Allocation and Scheduler Support"
depends on SMP
depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
+ depends on !X86_32 || !MEMORY_FAILURE
default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
---help---
Enable NUMA (Non Uniform Memory Access) support.
@@ -1125,6 +1127,9 @@ config NUMA
Otherwise, you should say N.
+comment "32bit NUMA support requires disabling MEMORY_FAILURE"
+ depends on X86_32 && MEMORY_FAILURE
+
comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
prev parent reply other threads:[~2009-09-26 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 12:51 [PULL] Please pull hwpoison code for 2.6.32 Andi Kleen
2009-09-26 14:13 ` [origin tree build failure] " Ingo Molnar
2009-09-26 15:17 ` Andi Kleen
2009-09-26 16:20 ` Andi Kleen
2009-09-26 17:28 ` Andi Kleen
2009-09-26 18:20 ` Andi Kleen
2009-09-26 16:35 ` Linus Torvalds
2009-09-26 17:35 ` [PATCH] x86: Fix hwpoison code related build failure on 32-bit NUMAQ Ingo Molnar
2009-09-26 17:43 ` Linus Torvalds
2009-09-26 18:10 ` Ingo Molnar
2009-09-26 18:12 ` Ingo Molnar
2009-09-26 18:11 ` Andi Kleen [this message]
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=20090926181134.GT30185@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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