Skip to contentSkip to conversation

why no Kconfig in "kernel" subdir?

DISCUSSION Chris Friesen 2 participants 4 messages Nov 14, 2003

lore
Share & tools
lore
#0 lore raw

I was adding a new general syscall the other day, and it struck me as odd that there is no Kconfig in the "kernel" subdirectory.

A quick search shows 36 separate config options being used in that subdirectory (stuff like PREEMPT, SMP, FUTEX, HOTPLUG, SYSCTL, etc). Why is there no Kconfig for it? As it stands, all of these have to be copied and pasted in every single arch. This seems odd.

Would people be open to a series of patches that create a new Kconfig and start moving generic stuff to it? Or are these things really arch-specific enough to warrent massive duplication?

Chris

Signature · 4 lines
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: [email protected]
#1 lore raw

On Fri, 14 Nov 2003 12:05:17 -0500 Chris Friesen <[email protected]> wrote:

| I was adding a new general syscall the other day, and it struck me as 
| odd that there is no Kconfig in the "kernel" subdirectory.
| 
| A quick search shows 36 separate config options being used in that 
| subdirectory (stuff like PREEMPT, SMP, FUTEX, HOTPLUG, SYSCTL, etc). 
| Why is there no Kconfig for it?  As it stands, all of these have to be 
| copied and pasted in every single arch.  This seems odd.

In several cases I expect that you are correct.
In some cases, general config options are now going into init/Kconfig.

| Would people be open to a series of patches that create a new Kconfig 
| and start moving generic stuff to it?  Or are these things really 
| arch-specific enough to warrent massive duplication?

I consider PREEMPT and SMP arch-specific, not generic.

Will init/Kconfig do what you want?

--
~Randy
MOTD: Always include version info.

#2 lore raw
Quoted 1 line · Randy.Dunlap

I consider PREEMPT and SMP arch-specific, not generic.

Interesting. Might I ask why? I thought that most of PREEMPT was pretty arch-neutral.

Quoted 1 line

Will init/Kconfig do what you want?

As long as there is some place to put generic options that are applicable to the system as a whole, then I'm happy.

Chris

Signature · 4 lines
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: [email protected]
#3 lore raw

On Fri, 14 Nov 2003 16:34:26 -0500 Chris Friesen <[email protected]> wrote:

| Randy.Dunlap wrote:
| 
| 
| > I consider PREEMPT and SMP arch-specific, not generic.
| 
| Interesting.  Might I ask why?  I thought that most of PREEMPT was 
| pretty arch-neutral.

Right, most of it is arch-neutral.
It appears that PA-RISC doesn't support PREEMPT:

include/asm-parisc/hardirq.h:
#ifdef CONFIG_PREEMPT

# error CONFIG_PREEMT currently not supported.
  [complete with typo]

and UML doesn't support PREEMPT either.

| > Will init/Kconfig do what you want?
| 
| As long as there is some place to put generic options that are 
| applicable to the system as a whole, then I'm happy.

I expect that it's workable.

--
~Randy
MOTD: Always include version info.