From: Adrian Bunk <bunk@stusta.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: Jes Sorensen <jes@sgi.com>, "'Keith Owens'" <kaos@sgi.com>,
"Luck, Tony" <tony.luck@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let IA64_GENERIC select more stuff
Date: Wed, 8 Feb 2006 23:49:04 +0100 [thread overview]
Message-ID: <20060208224904.GT3524@stusta.de> (raw)
In-Reply-To: <200602082224.k18MOpg24612@unix-os.sc.intel.com>
On Wed, Feb 08, 2006 at 02:24:51PM -0800, Chen, Kenneth W wrote:
> Adrian Bunk wrote on Wednesday, February 08, 2006 1:38 PM
> > > Not really, it helps a bit by selecting some things we know we need
> > > for all GENERIC builds. True we can't make it bullet proof, but whats
> > > there is better than removing it.
> >
> > Like the bug of allowing the illegal configuration NUMA=y, FLATMEM=y?
>
>
> You can't even compile a kernel with that combination ...
> Just about every arch except ia64 turns off ARCH_FLATMEM_ENABLE if NUMA=y.
> ia64 can just do the same thing. Instead of mucking around with select,
> fix the bug at its source. The real culprit is in mm/Kconfig, it shouldn't
> enable ARCH_FLATMEM_ENABLE if NUMA=y.
No, the bug is exactly the part of arch/ia64/Kconfig you are patching,
because mm/Kconfig simply relies on architectures setting the right
dependencies for ARCH_FLATMEM_ENABLE.
> Fix ARCH_FLATMEM_ENABLE dependency in ia64 arch.
>
> Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
>
> --- ./arch/ia64/Kconfig.orig 2006-02-08 14:57:40.597354431 -0800
> +++ ./arch/ia64/Kconfig 2006-02-08 15:04:15.552427718 -0800
> @@ -298,7 +298,8 @@ config ARCH_DISCONTIGMEM_ENABLE
> See <file:Documentation/vm/numa> for more.
>
> config ARCH_FLATMEM_ENABLE
> - def_bool y
> + depends on !NUMA
> + def_bool y if !NUMA
>...
Only one of the two NUMA dependencies is required.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-08 22:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 22:11 [2.6 patch] IA64_GENERIC shouldn't select other stuff Adrian Bunk
2006-02-07 22:37 ` Keith Owens
2006-02-07 22:43 ` Matthew Wilcox
2006-02-07 22:53 ` Adrian Bunk
2006-02-07 23:17 ` [2.6 patch] let IA64_GENERIC select more stuff Adrian Bunk
2006-02-08 0:52 ` Chen, Kenneth W
2006-02-08 1:19 ` Adrian Bunk
2006-02-08 1:40 ` Chen, Kenneth W
2006-02-08 2:08 ` Adrian Bunk
2006-02-08 2:17 ` Chen, Kenneth W
2006-02-08 2:43 ` Adrian Bunk
2006-02-08 2:48 ` Keith Owens
2006-02-08 2:54 ` Matthew Wilcox
2006-02-08 2:58 ` Chen, Kenneth W
2006-02-08 3:51 ` Adrian Bunk
2006-02-08 5:52 ` Chen, Kenneth W
2006-02-08 11:59 ` Adrian Bunk
2006-02-08 13:38 ` Jes Sorensen
2006-02-08 21:38 ` Adrian Bunk
2006-02-08 22:24 ` Chen, Kenneth W
2006-02-08 22:49 ` Adrian Bunk [this message]
2006-02-09 12:53 ` Jes Sorensen
2006-02-09 13:18 ` Matthew Wilcox
2006-02-09 13:26 ` Jes Sorensen
2006-02-09 14:16 ` Adrian Bunk
2006-02-09 15:19 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2006-02-08 18:35 Luck, Tony
2006-02-08 19:21 ` Alex Williamson
2006-02-08 19:24 ` Jes Sorensen
2006-02-08 19:55 ` Chen, Kenneth W
2006-02-08 21:24 ` Matthew Wilcox
2006-02-08 21:36 ` Chen, Kenneth W
2006-02-08 19:48 Luck, Tony
2006-02-08 22:35 Luck, Tony
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=20060208224904.GT3524@stusta.de \
--to=bunk@stusta.de \
--cc=jes@sgi.com \
--cc=kaos@sgi.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox