public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: 'Adrian Bunk' <bunk@stusta.de>,
	"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, 08 Feb 2006 02:48:10 +0000	[thread overview]
Message-ID: <10378.1139366890@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 07 Feb 2006 17:40:13 -0800." <200602080140.k181eDg20764@unix-os.sc.intel.com>
In-Reply-To: <20060207231713.GG3524@stusta.de>

"Chen, Kenneth W" (on Tue, 7 Feb 2006 17:40:13 -0800) 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.
>
>
>> 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
>with processor type, nor should it tied with ARCH_FLATMEM_ENABLE.  All
>of them are orthogonal and independent.

Blame me for the SMP bit.  I have a dim, distant memory that Intel
required all IA64 boxes to be SMP, but I could be wrong.  Also it is
almost pointless to do a generic build which pulls in NUMA etc.,
without also including SMP.


  parent reply	other threads:[~2006-02-08  2:48 UTC|newest]

Thread overview: 35+ 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 [this message]
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-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
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:48     ` Luck, Tony
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 22:24     ` Chen, Kenneth W
2006-02-08 22:49       ` Adrian Bunk
2006-02-08 22:35     ` Luck, Tony
2006-02-07 23:06 ` [2.6 patch] IA64_GENERIC shouldn't select other stuff 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=10378.1139366890@kao2.melbourne.sgi.com \
    --to=kaos@sgi.com \
    --cc=bunk@stusta.de \
    --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