Skip to contentSkip to conversation

IA64_GENERIC shouldn't select other stuff

PATCH In review Adrian Bunk 5 participants 26 messages Feb 7, 2006 – Feb 9, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 IA64_GENERIC shouldn't select other stuff

IA64_GENERIC shouldn't select other stuff.

select'ing ACPI without select'ing PCI had broken ACPI in the past (the current workaround is that ACPI select's PCI).

Select'ing NUMA means that the illegal configuration NUMA=y, FLATMEM=y is possible.

The generic setting might be required in some places, but select'ing some options like NUMA while not select'ing some other similar important options like PCI doesn't make much sense.

arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +0 -3
@@ -72,9 +72,6 @@
 
 config IA64_GENERIC
 	bool "generic"
-	select ACPI
-	select NUMA
-	select ACPI_NUMA
 	help
 	  This selects the system type of your hardware.  A "generic" kernel
 	  will run on any supported IA-64 system.  However, if you configure
#1 lore raw
Quoted 24 lines · Adrian Bunk (on Tue, 7 Feb 2006 23:11:57 +0100) wrote:

IA64_GENERIC shouldn't select other stuff.

select'ing ACPI without select'ing PCI had broken ACPI in the past (the current workaround is that ACPI select's PCI).

Select'ing NUMA means that the illegal configuration NUMA=y, FLATMEM=y is possible.

The generic setting might be required in some places, but select'ing some options like NUMA while not select'ing some other similar important options like PCI doesn't make much sense.

arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +0 -0
@@ -72,9 +72,6 @@
 

config IA64_GENERIC
bool "generic"

arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +0 -3
-	select ACPI
-	select NUMA
-	select ACPI_NUMA
Quoted 4 lines

help
This selects the system type of your hardware. A "generic" kernel will run on any supported IA-64 system. However, if you configure

A generic IA64 kernel requires (at least) the ACPI and NUMA options in order to run on all the IA64 platforms out there. Omitting those options and relying on the user to set them by hand is going to cause more problems.

If anything, there should be more options being set as a side effect of selecting IA64_GENERIC, including ARCH_DISCONTIGMEM_ENABLE, ARCH_SPARSEMEM_ENABLE, PCI and even SMP.

#2 lore raw
Quoted 4 lines · Keith Owens

A generic IA64 kernel requires (at least) the ACPI and NUMA options in order to run on all the IA64 platforms out there. Omitting those options and relying on the user to set them by hand is going to cause more problems.

I'm not sure about that. If the user selects a specific type of machine, ACPI doesn't get selected for them -- even when it's needed to boot. It's certainly inconsistent and should be fixed one way or the other.

#3 lore raw
Quoted 9 lines · Matthew Wilcox
Quoted 4 lines · Keith Owens

A generic IA64 kernel requires (at least) the ACPI and NUMA options in order to run on all the IA64 platforms out there. Omitting those options and relying on the user to set them by hand is going to cause more problems.

I'm not sure about that. If the user selects a specific type of machine, ACPI doesn't get selected for them -- even when it's needed to boot. It's certainly inconsistent and should be fixed one way or the other.

And PCI is never selected for him with IA64_GENERIC.

I see the point for a catch-all option for processor-specific stuff, but it can't be a replacement for allyesconfig.

AFAIR your defconfig was intended for the "runs everywhere" case (with the exception that in this case the bug that CONFIG_ITANIUM is not set is still unfixed - would you accept a patch to fix this?).

cu
Adrian

Signature · 4 lines
       "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
#4 lore raw

PATCH 1/1 let IA64_GENERIC select more stuff

In reply to Keith Owens
Quoted 9 lines · Keith Owens

A generic IA64 kernel requires (at least) the ACPI and NUMA options in order to run on all the IA64 platforms out there. Omitting those options and relying on the user to set them by hand is going to cause more problems.

If anything, there should be more options being set as a side effect of selecting IA64_GENERIC, including ARCH_DISCONTIGMEM_ENABLE, ARCH_SPARSEMEM_ENABLE, PCI and even SMP.

IOW, you want the patch below?

Not that I'm a big fan of this approach, but if it should be done this way, it should be done right.

cu
Adrian

<-- snip -->

Let IA64_GENERIC select more stuff (as wanted by the ia64 developers).

arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +4 -1
@@ -73,10 +73,12 @@
 config IA64_GENERIC
 	bool "generic"
 	select ACPI
 	select NUMA
 	select ACPI_NUMA
+	select PCI
+	select SMP
 	help
 	  This selects the system type of your hardware.  A "generic" kernel
 	  will run on any supported IA-64 system.  However, if you configure
 	  a kernel for your specific system, it will be faster and smaller.
 
@@ -132,10 +134,11 @@
 	  This choice is safe for all IA-64 systems, but may not perform
 	  optimally on systems with, say, Itanium 2 or newer processors.
 
 config MCKINLEY
 	bool "Itanium 2"
+	depends on IA64_GENERIC=n
 	help
 	  Select this to configure for an Itanium 2 (McKinley) processor.
 
 endchoice
 
@@ -318,11 +321,11 @@
 	  for architectures which are either NUMA (Non-Uniform Memory Access)
 	  or have huge holes in the physical address space for other reasons.
  	  See <file:Documentation/vm/numa> for more.
 
 config ARCH_FLATMEM_ENABLE
-	def_bool y
+	def_bool y if IA64_GENERIC=n
 
 config ARCH_SPARSEMEM_ENABLE
 	def_bool y
 	depends on ARCH_DISCONTIGMEM_ENABLE
 
#5 lore raw

RE: [2.6 patch] let IA64_GENERIC select more stuff

Adrian Bunk wrote on Tuesday, February 07, 2006 3:17 PM

Quoted 2 lines

IOW, you want the patch below?

No, I really don't think so.

Quoted 4 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +0 -0
@@ -132,10 +134,11 @@
 	  This choice is safe for all IA-64 systems, but may not perform

arch/ia64/Kconfig line 144

Quoted 10 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +1 -0
 	  optimally on systems with, say, Itanium 2 or newer processors.
 
 config MCKINLEY
 	bool "Itanium 2"
+	depends on IA64_GENERIC=n
 	help
 	  Select this to configure for an Itanium 2 (McKinley) processor.
 
 endchoice
 

This hunk does not make any logical sense. Select generic system type does not mean Itanium processor is the only choice I can have. What's wrong with having an option that works just fine right now?

- Ken

#6 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 19 lines · Kenneth W

Adrian Bunk wrote on Tuesday, February 07, 2006 3:17 PM

Quoted 2 lines

IOW, you want the patch below?

No, I really don't think so.

Quoted 12 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +1 -0
@@ -132,10 +134,11 @@
 	  This choice is safe for all IA-64 systems, but may not perform
 	  optimally on systems with, say, Itanium 2 or newer processors.
 
 config MCKINLEY
 	bool "Itanium 2"
+	depends on IA64_GENERIC=n
 	help
 	  Select this to configure for an Itanium 2 (McKinley) processor.
 
Quoted 6 lines

arch/ia64/Kconfig line 144

Quoted 2 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +0 -0
 endchoice
 

This hunk does not make any logical sense. Select generic system type does not mean Itanium processor is the only choice I can have. What's wrong with having an option that works just fine right now?

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?

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.

Quoted 1 line

- Ken

cu
Adrian

Signature · 4 lines
       "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
#7 lore raw

RE: [2.6 patch] let IA64_GENERIC select more stuff

Adrian Bunk wrote on Tuesday, February 07, 2006 5:20 PM

Quoted 3 lines

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.

Quoted 2 lines

Keith said IA64_GENERIC should select all the options required in order to run on all the IA64 platforms out there.

                          ^^^^^^^^^^^^^^
Quoted 1 line

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.

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.

- Ken

#8 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 7 lines · Kenneth W

Adrian Bunk wrote on Tuesday, February 07, 2006 5:20 PM

Quoted 3 lines

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 ...

Quoted 8 lines

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.

Quoted 7 lines
Quoted 2 lines

Keith said IA64_GENERIC should select all the options required in order to run on all the IA64 platforms out there.

                          ^^^^^^^^^^^^^^
Quoted 1 line

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.

Quoted 2 lines

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... ;-)

Quoted 3 lines

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.

Quoted 1 line

- Ken

cu
Adrian

Signature · 4 lines
       "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
#9 lore raw

RE: [2.6 patch] let IA64_GENERIC select more stuff

Adrian Bunk wrote on Tuesday, February 07, 2006 6:09 PM

Quoted 11 lines
Quoted 8 lines

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.

Right, that is what Matthew Wilcox said in earlier thread.

Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

Keith said IA64_GENERIC should select all the options required in order to run on all the IA64 platforms out there.

                          ^^^^^^^^^^^^^^
Quoted 1 line

This is what my patch does.

Quoted 7 lines
Quoted 2 lines

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.

You have to digest what people say and *understand* why they said what they say. Checking earlier thread, Keith did not say "select CONFIG_ITANIUM for generic ia64 platforms".

Quoted 7 lines
Quoted 3 lines

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.

This is going too far and very childish in my opinion. I'm going to shut up.

- Ken

#10 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 26 lines · Kenneth W

Adrian Bunk wrote on Tuesday, February 07, 2006 6:09 PM

Quoted 11 lines
Quoted 8 lines

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.

Right, that is what Matthew Wilcox said in earlier thread.

Quoted 10 lines
Quoted 7 lines
Quoted 2 lines

Keith said IA64_GENERIC should select all the options required in order to run on all the IA64 platforms out there.

                          ^^^^^^^^^^^^^^
Quoted 1 line

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.

Quoted 7 lines
Quoted 2 lines

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.

You have to digest what people say and *understand* why they said what they say. Checking earlier thread, Keith did not say "select CONFIG_ITANIUM for generic ia64 platforms".
...

Keith suggested that IA64_GENERIC should select SMP, and this is what you disagreed with.

And I'm still interested in your suggestion for the IA64_GENERIC<->NUMA<->FLATMEM dependencies.

Quoted 1 line

- Ken

cu
Adrian

Signature · 4 lines
       "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
#11 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

In reply to Chen, Kenneth W
Quoted 19 lines · "Chen, Kenneth W" (on Tue, 7 Feb 2006 17:40:13 -0800) wrote:

Adrian Bunk wrote on Tuesday, February 07, 2006 5:20 PM

Quoted 3 lines

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.

Quoted 2 lines

Keith said IA64_GENERIC should select all the options required in order to run on all the IA64 platforms out there.

Quoted 7 lines
                         ^^^^^^^^^^^^^^
Quoted 1 line

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.

#12 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 2 lines · Keith Owens

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

The HP zx2000 is a single socket workstation, and you can buy other HP workstations/servers with only one socket occupied.

#13 lore raw

RE: [2.6 patch] let IA64_GENERIC select more stuff

In reply to Keith Owens

Keith Owens wrote on Tuesday, February 07, 2006 6:48 PM

Quoted 9 lines
Quoted 4 lines

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.

I'm not disagreeing with the SMP bit. In my very first reply, I disagree with the hunk that disable CONFIG_MCKINLEY for CONFIG_IA64_GENERIC. People tends to mix the terminology, CONFIG_IA64_GENERIC is a platform type choice, it is a sub-requirement for building a kernel that boots everywhere. People keeps on promoting the config option.

- Ken

Excerpt from earlier email:

Quoted 4 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +0 -0
@@ -132,10 +134,11 @@
 	  This choice is safe for all IA-64 systems, but may not perform

arch/ia64/Kconfig line 144

Quoted 10 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.old +1 -0
 	  optimally on systems with, say, Itanium 2 or newer processors.
 
 config MCKINLEY
 	bool "Itanium 2"
+	depends on IA64_GENERIC=n
 	help
 	  Select this to configure for an Itanium 2 (McKinley) processor.
 
 endchoice
 

This hunk does not make any logical sense. Select generic system type does not mean Itanium processor is the only choice I can have. What's wrong with having an option that works just fine right now?

#14 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 6 lines · Kenneth W

...

Quoted 2 lines
Quoted 2 lines

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

...
I'm not disagreeing with the SMP bit. In my very first reply, I
...

It might be related to the fact that I'm not a native English speaker, but for me this reads as if you contradict yourself, and I have therefore problems understanding your emails.

Quoted 2 lines

- Ken
...

cu
Adrian

Signature · 4 lines
       "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
#15 lore raw

RE: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines

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

...
I'm not disagreeing with the SMP bit. In my very first reply, I
...

It might be related to the fact that I'm not a native English speaker, but for me this reads as if you contradict yourself, and I have therefore problems understanding your emails.

Yeah, I've been flip-flopping on CONFIG_SMP. I just don't have strong opinion one way or the other. Having said that, I don't think we should mix the CONFIG_IA64_GENERIC, which is defined to select platform type with smp/processor type etc.

But for the bit that this thread started, which disables CONFIG_MCKINLEY for CONFIG_IA64_GENERIC, it is totally wrong and is the "over my dead body" type of thing.

- Ken

#16 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 10 lines · Kenneth W
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines

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

...
I'm not disagreeing with the SMP bit. In my very first reply, I
...

It might be related to the fact that I'm not a native English speaker, but for me this reads as if you contradict yourself, and I have therefore problems understanding your emails.

Quoted 8 lines

Yeah, I've been flip-flopping on CONFIG_SMP. I just don't have strong opinion one way or the other. Having said that, I don't think we should mix the CONFIG_IA64_GENERIC, which is defined to select platform type with smp/processor type etc.

But for the bit that this thread started, which disables CONFIG_MCKINLEY for CONFIG_IA64_GENERIC, it is totally wrong and is the "over my dead body" type of thing.

My initial patch that started this thread was to remove all select's from CONFIG_IA64_GENERIC.

Is this OK for you?

Quoted 1 line

- Ken

cu
Adrian

Signature · 4 lines
       "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
#17 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Adrian" = Adrian Bunk <[email protected]> writes:

Adrian> On Tue, Feb 07, 2006 at 09:52:09PM -0800, Chen, Kenneth W

Quoted 3 lines · Adrian> wrote:
Quoted 3 lines

But for the bit that this thread started, which disables CONFIG_MCKINLEY for CONFIG_IA64_GENERIC, it is totally wrong and is the "over my dead body" type of thing.

Adrian> My initial patch that started this thread was to remove all Adrian> select's from CONFIG_IA64_GENERIC.

Adrian> Is this OK for you?

Adrian,

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.

Jes

#18 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 11 lines · Jes Sorensen
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Adrian" = Adrian Bunk <[email protected]> writes:

Adrian> On Tue, Feb 07, 2006 at 09:52:09PM -0800, Chen, Kenneth W

Quoted 3 lines · Adrian> wrote:
Quoted 3 lines

But for the bit that this thread started, which disables CONFIG_MCKINLEY for CONFIG_IA64_GENERIC, it is totally wrong and is the "over my dead body" type of thing.

Adrian> My initial patch that started this thread was to remove all Adrian> select's from CONFIG_IA64_GENERIC.

Quoted 7 lines

Adrian> Is this OK for you?

Adrian,

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?

Quoted 1 line

Jes

cu
Adrian

Signature · 4 lines
       "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
#19 lore raw

RE: [2.6 patch] let IA64_GENERIC select more stuff

Adrian Bunk wrote on Wednesday, February 08, 2006 1:38 PM

Quoted 5 lines
Quoted 3 lines

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.

Fix ARCH_FLATMEM_ENABLE dependency in ia64 arch.

arch/ia64/Kconfig renamed from arch/ia64/Kconfig.orig +2 -1
@@ -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
 
 config ARCH_SPARSEMEM_ENABLE
 	def_bool y
#20 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 5 lines · Kenneth W

Adrian Bunk wrote on Wednesday, February 08, 2006 1:38 PM

Quoted 4 lines
Quoted 3 lines

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.

Quoted 8 lines
Quoted 1 line

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.

Quoted 7 lines

Fix ARCH_FLATMEM_ENABLE dependency in ia64 arch.

arch/ia64/Kconfig config ARCH_DISCONTIGMEM_ENABLE · line 302

Quoted 7 lines
arch/ia64/Kconfig renamed from arch/ia64/Kconfig.orig +2 -1
@@ -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

Signature · 4 lines
       "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
#21 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

In reply to Adrian Bunk
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Adrian" = Adrian Bunk <[email protected]> writes:

Quoted 3 lines · Jes Sorensen
Quoted 3 lines

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.

Adrian> Like the bug of allowing the illegal configuration NUMA=y, Adrian> FLATMEM=y?

Adrian,

There's other reasons why this is a moot exercise anyway, allyesconfig doesn't link on ia64 due to the size of the object exceeding the reach of the relative link relocs. Not much you can do about that.

Here's a patch that will make it all build until it tries to link. It includes a simplified version of Ken's patch. Now can we please dismiss this issue once and for all and go back to getting real work done?

Tony, would you apply at least the part of this touching arch/ia64/Kconfig if you do not fancy taking it all, please.

Thanks,
Jes

Various fixes to help allyesconfig on ia64:
- ARCH_FLATMEM_ENABLE is incompatible with NUMA
- atm code tries to include kernel headers to decide upon byteorder without allowing for said header file to include other files
- HP100 driver cannot be compiled on systems without ISA support in it's current state.
- Add check_signature() to include/asm-ia64/io.h
- Include vmalloc.h in mixart_hwdep.c which uses vmalloc

----

 arch/ia64/Kconfig               |    1 +
 drivers/atm/Makefile            |    2 +-
 drivers/net/Kconfig             |    2 +-
 include/asm-ia64/io.h           |   15 +++++++++++++++
 sound/pci/mixart/mixart_hwdep.c |    1 +
 5 files changed, 19 insertions(+), 2 deletions(-)

Index: linux-2.6/arch/ia64/Kconfig =================================--- linux-2.6.orig/arch/ia64/Kconfig +++ linux-2.6/arch/ia64/Kconfig
@@ -297,6 +297,7 @@
See <file:Documentation/vm/numa> for more.

config ARCH_FLATMEM_ENABLE
+ depends on !NUMA
def_bool y

config ARCH_SPARSEMEM_ENABLE
Index: linux-2.6/drivers/atm/Makefile =================================--- linux-2.6.orig/drivers/atm/Makefile +++ linux-2.6/drivers/atm/Makefile
@@ -41,7 +41,7 @@

   # guess the target endianess to choose the right PCA-200E firmware image
   ifeq ($(CONFIG_ATM_FORE200E_PCA_DEFAULT_FW),y)
     byteorder.h			:= include$(if $(patsubst $(srctree),,$(objtree)),2)/asm/byteorder.h
-    CONFIG_ATM_FORE200E_PCA_FW	:= $(obj)/pca200e$(if $(shell $(CC) -E -dM $(byteorder.h) | grep ' __LITTLE_ENDIAN '),.bin,_ecd.bin2)
+    CONFIG_ATM_FORE200E_PCA_FW	:= $(obj)/pca200e$(if $(shell $(CC) -I$(srctree)/include -E -dM $(byteorder.h) | grep ' __LITTLE_ENDIAN '),.bin,_ecd.bin2)
   endif
 endif

Index: linux-2.6/drivers/net/Kconfig =================================--- linux-2.6.orig/drivers/net/Kconfig +++ linux-2.6/drivers/net/Kconfig
@@ -946,7 +946,7 @@

config HP100
tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
- depends on NET_ETHERNET && (ISA || EISA || PCI)
+ depends on NET_ETHERNET && ISA || EISA
help
If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from
Index: linux-2.6/include/asm-ia64/io.h =================================--- linux-2.6.orig/include/asm-ia64/io.h +++ linux-2.6/include/asm-ia64/io.h
@@ -435,6 +435,21 @@

#define ioremap_nocache(o,s) ioremap(o,s)

+static inline int
+check_signature(void __iomem *io_addr, const unsigned char *signature,
+ int length)
+{
+ int retval = 0;
+ do {
+ if (readb(io_addr) != *signature++)
+ goto out;
+ io_addr++;
+ } while (--length);
+ retval = 1;
+ out:
+ return retval;
+}
+

 # ifdef __KERNEL__

/*
Index: linux-2.6/sound/pci/mixart/mixart_hwdep.c =================================--- linux-2.6.orig/sound/pci/mixart/mixart_hwdep.c +++ linux-2.6/sound/pci/mixart/mixart_hwdep.c
@@ -24,6 +24,7 @@
#include <linux/interrupt.h>
#include <linux/pci.h>
#include <linux/firmware.h>
+#include <linux/vmalloc.h>
#include <asm/io.h>
#include <sound/core.h>
#include "mixart.h"

#22 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 3 lines · Jes Sorensen

There's other reasons why this is a moot exercise anyway, allyesconfig doesn't link on ia64 due to the size of the object exceeding the reach of the relative link relocs. Not much you can do about that.

That'd be a toolchain problem then ... need to insert stubs.

Quoted 2 lines

- HP100 driver cannot be compiled on systems without ISA support in it's current state.

I have it enabled on parisc without ISA or EISA. More details, please.

Review

Quoted 5 lines

config HP100

(quoted diff) +1 -1
 	tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
-	depends on NET_ETHERNET && (ISA || EISA || PCI)
+	depends on NET_ETHERNET && ISA || EISA
 	help

Also I think this is wrong. Doesn't the precedence make this evaluate as (NET_ETHERNET && ISA) || EISA ?

#23 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Matthew" = Matthew Wilcox <[email protected]> writes:

Quoted 4 lines · Jes Sorensen
Quoted 4 lines

There's other reasons why this is a moot exercise anyway, allyesconfig doesn't link on ia64 due to the size of the object exceeding the reach of the relative link relocs. Not much you can do about that.

Matthew> That'd be a toolchain problem then ... need to insert stubs.

True, but I think there's a special flag people need to use when linking large userland apps. No idea if it could work for the kernel in this case.

Quoted 2 lines
Quoted 2 lines

- HP100 driver cannot be compiled on systems without ISA support in it's current state.

Matthew> I have it enabled on parisc without ISA or EISA. More Matthew> details, please.

Generous use of isa_memcpy_toio, isa_readb etc. Those functions ought not be visible in a config where ISA is disabled. Anybody who cares enough about this could easily fix the HP100 driver to deal with it, but it would require some reorganization of the code.

Quoted 3 lines
Quoted 3 lines

config HP100 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
- depends on NET_ETHERNET && (ISA || EISA || PCI) + depends on NET_ETHERNET && ISA || EISA help

Matthew> Also I think this is wrong. Doesn't the precedence make this Matthew> evaluate as (NET_ETHERNET && ISA) || EISA ?

Thats me being stupid, the parenthesis should have stayed.

Updated patch attached.

Cheers,
Jes

Various fixes to help allyesconfig on ia64:
- ARCH_FLATMEM_ENABLE is incompatible with NUMA
- atm code tries to include kernel headers to decide upon byteorder without allowing for said header file to include other files
- HP100 driver cannot be compiled on systems without ISA support in it's current state.
- Add check_signature() to include/asm-ia64/io.h
- Include vmalloc.h in mixart_hwdep.c which uses vmalloc

----

 arch/ia64/Kconfig               |    1 +
 drivers/atm/Makefile            |    2 +-
 drivers/net/Kconfig             |    2 +-
 include/asm-ia64/io.h           |   15 +++++++++++++++
 sound/pci/mixart/mixart_hwdep.c |    1 +
 5 files changed, 19 insertions(+), 2 deletions(-)

Index: linux-2.6/arch/ia64/Kconfig =================================--- linux-2.6.orig/arch/ia64/Kconfig +++ linux-2.6/arch/ia64/Kconfig
@@ -297,6 +297,7 @@
See <file:Documentation/vm/numa> for more.

config ARCH_FLATMEM_ENABLE
+ depends on !NUMA
def_bool y

config ARCH_SPARSEMEM_ENABLE
Index: linux-2.6/drivers/atm/Makefile =================================--- linux-2.6.orig/drivers/atm/Makefile +++ linux-2.6/drivers/atm/Makefile
@@ -41,7 +41,7 @@

   # guess the target endianess to choose the right PCA-200E firmware image
   ifeq ($(CONFIG_ATM_FORE200E_PCA_DEFAULT_FW),y)
     byteorder.h			:= include$(if $(patsubst $(srctree),,$(objtree)),2)/asm/byteorder.h
-    CONFIG_ATM_FORE200E_PCA_FW	:= $(obj)/pca200e$(if $(shell $(CC) -E -dM $(byteorder.h) | grep ' __LITTLE_ENDIAN '),.bin,_ecd.bin2)
+    CONFIG_ATM_FORE200E_PCA_FW	:= $(obj)/pca200e$(if $(shell $(CC) -I$(srctree)/include -E -dM $(byteorder.h) | grep ' __LITTLE_ENDIAN '),.bin,_ecd.bin2)
   endif
 endif

Index: linux-2.6/drivers/net/Kconfig =================================--- linux-2.6.orig/drivers/net/Kconfig +++ linux-2.6/drivers/net/Kconfig
@@ -946,7 +946,7 @@

config HP100
tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"

-	depends on NET_ETHERNET && (ISA || EISA || PCI)
+	depends on NET_ETHERNET && (ISA || EISA)

help
If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from
Index: linux-2.6/include/asm-ia64/io.h =================================--- linux-2.6.orig/include/asm-ia64/io.h +++ linux-2.6/include/asm-ia64/io.h
@@ -435,6 +435,21 @@

#define ioremap_nocache(o,s) ioremap(o,s)

+static inline int
+check_signature(void __iomem *io_addr, const unsigned char *signature,
+ int length)
+{
+ int retval = 0;
+ do {
+ if (readb(io_addr) != *signature++)
+ goto out;
+ io_addr++;
+ } while (--length);
+ retval = 1;
+ out:
+ return retval;
+}
+

 # ifdef __KERNEL__

/*
Index: linux-2.6/sound/pci/mixart/mixart_hwdep.c =================================--- linux-2.6.orig/sound/pci/mixart/mixart_hwdep.c +++ linux-2.6/sound/pci/mixart/mixart_hwdep.c
@@ -24,6 +24,7 @@
#include <linux/interrupt.h>
#include <linux/pci.h>
#include <linux/firmware.h>
+#include <linux/vmalloc.h>
#include <asm/io.h>
#include <sound/core.h>
#include "mixart.h"

#24 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 5 lines · Jes Sorensen
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Matthew" = Matthew Wilcox <[email protected]> writes:

...

Quoted 2 lines
Quoted 2 lines

- HP100 driver cannot be compiled on systems without ISA support in it's current state.

Quoted 8 lines

Matthew> I have it enabled on parisc without ISA or EISA. More Matthew> details, please.

Generous use of isa_memcpy_toio, isa_readb etc. Those functions ought not be visible in a config where ISA is disabled. Anybody who cares enough about this could easily fix the HP100 driver to deal with it, but it would require some reorganization of the code.
...

A patch is already available:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/
2.6.16-rc2/2.6.16-rc2-mm1/broken-out/ remove-isa-legacy-functions-drivers-net-hp100c.patch

cu
Adrian

Signature · 4 lines
       "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
#25 lore raw

Re: [2.6 patch] let IA64_GENERIC select more stuff

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Adrian" = Adrian Bunk <[email protected]> writes:

Adrian> A patch is already available:

Adrian> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/ Adrian> 2.6.16-rc2/2.6.16-rc2-mm1/broken-out/
Adrian> remove-isa-legacy-functions-drivers-net-hp100c.patch

No problem, Al's patch looks a better solution than mine. So lets ignore that part of my patch.

Tony is it ok for you to just ignore that part of the patch and apply the rest? If not I can send you an updated patch.

Thanks,
Jes