From: Jan Beulich <jbeulich@novell.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
jbeulich@novell.com, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/mm] x86, 32-bit: also limit NODES_HIGH_SHIFT here
Date: Fri, 13 Mar 2009 02:33:38 GMT [thread overview]
Message-ID: <tip-46d50c98d90cd7feaa5977a09c574063e5c99b3d@git.kernel.org> (raw)
In-Reply-To: <49B90F12.76E4.0078.0@novell.com>
Commit-ID: 46d50c98d90cd7feaa5977a09c574063e5c99b3d
Gitweb: http://git.kernel.org/tip/46d50c98d90cd7feaa5977a09c574063e5c99b3d
Author: Jan Beulich <jbeulich@novell.com>
AuthorDate: Thu, 12 Mar 2009 12:33:06 +0000
Commit: Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 13 Mar 2009 02:37:17 +0100
x86, 32-bit: also limit NODES_HIGH_SHIFT here
Impact: configuration bug fix
Just like for x86-64, the range of widths valid for NODE_SHIFT is not
unbounded. The upper bound 64-bit uses is definitely also an upper
bound for 32-bit.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
LKML-Reference: <49B90F12.76E4.0078.0@novell.com>
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 87717f3..076f4f8 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1123,7 +1123,7 @@ config NUMA_EMU
config NODES_SHIFT
int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
- range 1 9 if X86_64
+ range 1 9
default "9" if MAXSMP
default "6" if X86_64
default "4" if X86_NUMAQ
prev parent reply other threads:[~2009-03-13 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 12:33 [PATCH, resend] i386: also limit NODES_HIGH_SHIFT here Jan Beulich
2009-03-12 13:29 ` Andi Kleen
2009-03-13 2:33 ` Jan Beulich [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=tip-46d50c98d90cd7feaa5977a09c574063e5c99b3d@git.kernel.org \
--to=jbeulich@novell.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