From: Adrian Bunk <bunk@stusta.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: 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 03:08:32 +0100 [thread overview]
Message-ID: <20060208020832.GK3524@stusta.de> (raw)
In-Reply-To: <200602080140.k181eDg20764@unix-os.sc.intel.com>
On Tue, Feb 07, 2006 at 05:40:13PM -0800, Chen, Kenneth W wrote:
> Adrian Bunk wrote on Tuesday, February 07, 2006 5:20 PM
> > You could ask the same question for NUMA:
> > Select generic system type does not mean NUMA systems are only choice I
> > can have. What's wrong with having an option that works just fine?
>
> Please read more ia64 arch specific code ...
>
> CONFIG_IA64_GENERIC is a platform type choice, you can have platform
> type of DIG, HPZX1, SGI SN2, or all of the above. DIG platform depends
> on ACPI, thus need ACPI on. SGI altix is a numa box, thus, need NUMA
> on. NEC, Fujitsu build numa machines with ACPI SRAT table, thus, need
> ACPI_NUMA on. When you build a kernel to boot on all platforms, you
> have no choice but to turn on all of the above. Processor type and SMP
> is different from platform type. It does not have any dependency on
> platform type. They are orthogonal choice.
This is interesting, considering that e.g. IA64_SGI_SN2=y, NUMA=n or
IA64_DIG=y, ACPI=n are currently allowed configurations.
> > Keith said IA64_GENERIC should select all the options required in
> > order to run on all the IA64 platforms out there.
> ^^^^^^^^^^^^^^
> > This is what my patch does.
>
> You patch does more than what you described and is wrong. Selecting
> platform type should not be tied into selecting SMP nor should it tied
This was what Keith wanted.
It seems everyone thinks I am wrong, but when I'm implementing what one
person suggests, other people say that what I am doing is wrong.
> with processor type, nor should it tied with ARCH_FLATMEM_ENABLE. All
> of them are orthogonal and independent.
1. NUMA on ia64 currently depends on !FLATMEM.
2. IA64_GENERIC currently select's NUMA.
3. You say IA64_GENERIC should not be tied with ARCH_FLATMEM_ENABLE.
It's impossible to fulfill all three of them.
My initial approach to fix them was to remove the select's from
IA64_GENERIC, therefore removing 2., but this patch was not accepted.
This patch adds more select's to IA64_GENERIC, therefore removing 3.,
but you disagree with it.
The last choice it to remove the dependency of NUMA on !FLATMEM... ;-)
> Theoretically and maybe academically interesting, I should be able to
> build a kernel that boots on all UP platforms, with your patch, that
> is not possible.
Theoretically and maybe academically interesting, I should be able to
build a kernel that boots on all non-NUMA platforms, currently, that is
not possible.
> - Ken
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 2:08 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 [this message]
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
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=20060208020832.GK3524@stusta.de \
--to=bunk@stusta.de \
--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