Skip to contentSkip to conversation

strange CRASH_DUMP dependencies

DISCUSSION Adrian Bunk 3 participants 6 messages Aug 21, 2005 – Aug 23, 2005

lore
Share & tools
lore
#0 lore raw

config CRASH_DUMP
bool "kernel crash dumps (EXPERIMENTAL)" depends on EMBEDDED
depends on EXPERIMENTAL
depends on HIGHMEM
help
Generate crash dump after being started by kexec.

Two questions:
- If it has any dependencies on kexec, why isn't there a dependency?
- Is there any sane reason for the dependency on EMBEDDED?

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
#1 lore raw
Quoted 10 lines · Adrian Bunk

config CRASH_DUMP
bool "kernel crash dumps (EXPERIMENTAL)" depends on EMBEDDED
depends on EXPERIMENTAL
depends on HIGHMEM
help
Generate crash dump after being started by kexec.

Two questions:
- If it has any dependencies on kexec, why isn't there a dependency?

crashdump has got dependency on kexec but not in the same kernel. What I mean is that as of today two kernels are involved in this process. First kernel is crashing kernel which should have enabled CONFIG_KEXEC and second kernel (capture kernel) is one which captures the dump and should have CONFIG_CRASH_DUMP enabled. Second kernel need not to have CONFIG_KEXEC enabled for catpturing dump. Hence CRASH_DUMP is not directly dependent on CONFIG_KEXEC.

Quoted 2 lines

- Is there any sane reason for the dependency on EMBEDDED?

I believe this was introduced because large servers can have huge amount of memory (running into Tera Bytes) and saving all that memory might not be practical. Hence it was perceived that until some filtering mechanism is implemented, it is more suited for small systems.

Personally I think it can be gotten away with because as a developer I can run gdb directly on /proc/vmcore and need not to save the whole memory hence need not to restrict this feature only for small systems.

Eric, do you think otherwise?

Thanks
Vivek

#2 lore raw
Quoted 12 lines · Vivek Goyal
Quoted 10 lines · Adrian Bunk

config CRASH_DUMP
bool "kernel crash dumps (EXPERIMENTAL)" depends on EMBEDDED
depends on EXPERIMENTAL
depends on HIGHMEM
help
Generate crash dump after being started by kexec.

Two questions:
- If it has any dependencies on kexec, why isn't there a dependency?

Quoted 7 lines

crashdump has got dependency on kexec but not in the same kernel. What I mean is that as of today two kernels are involved in this process. First kernel is crashing kernel which should have enabled CONFIG_KEXEC and second kernel (capture kernel) is one which captures the dump and should have CONFIG_CRASH_DUMP enabled. Second kernel need not to have CONFIG_KEXEC enabled for catpturing dump. Hence CRASH_DUMP is not directly dependent on CONFIG_KEXEC.

Sounds reasonable.

Quoted 8 lines
Quoted 2 lines

- Is there any sane reason for the dependency on EMBEDDED?

I believe this was introduced because large servers can have huge amount of memory (running into Tera Bytes) and saving all that memory might not be practical. Hence it was perceived that until some filtering mechanism is implemented, it is more suited for small systems.
...

It seems you have a wrong impression of what EMBEDDED in the kernel does.

There is _not_ a choice EMBEDDED/WORKSTATION/SERVER.

EMBEDDED is an option that shows "save space at any cost" options.

It allows you to tell gcc to generate slower but faster code or to deselect options in the "do this only if you _really_ know what you are doing" class.

Quoted 2 lines

Thanks
Vivek

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
#3 lore raw
Quoted 12 lines · Adrian Bunk
Quoted 8 lines
Quoted 2 lines

- Is there any sane reason for the dependency on EMBEDDED?

I believe this was introduced because large servers can have huge amount of memory (running into Tera Bytes) and saving all that memory might not be practical. Hence it was perceived that until some filtering mechanism is implemented, it is more suited for small systems.
...

It seems you have a wrong impression of what EMBEDDED in the kernel does.

Quoted 7 lines

There is _not_ a choice EMBEDDED/WORKSTATION/SERVER.

EMBEDDED is an option that shows "save space at any cost" options.

It allows you to tell gcc to generate slower but faster code or to deselect options in the "do this only if you _really_ know what you are doing" class.

And at the moment that is where building a crashdump capture kernel falls. "do this only if you really know what you are doing".

Eric

#4 lore raw
In reply to Adrian Bunk
Quoted 26 lines · Adrian Bunk
Quoted 12 lines · Vivek Goyal
Quoted 10 lines · Adrian Bunk

config CRASH_DUMP
bool "kernel crash dumps (EXPERIMENTAL)" depends on EMBEDDED
depends on EXPERIMENTAL
depends on HIGHMEM
help
Generate crash dump after being started by kexec.

Two questions:
- If it has any dependencies on kexec, why isn't there a dependency?

Quoted 7 lines

crashdump has got dependency on kexec but not in the same kernel. What I mean is that as of today two kernels are involved in this process. First kernel is crashing kernel which should have enabled CONFIG_KEXEC and second kernel (capture kernel) is one which captures the dump and should have CONFIG_CRASH_DUMP enabled. Second kernel need not to have CONFIG_KEXEC enabled for catpturing dump. Hence CRASH_DUMP is not directly dependent on CONFIG_KEXEC.

Sounds reasonable.

Quoted 3 lines
Quoted 2 lines

- Is there any sane reason for the dependency on EMBEDDED?

Quoted 9 lines
Quoted 5 lines

I believe this was introduced because large servers can have huge amount of memory (running into Tera Bytes) and saving all that memory might not be practical. Hence it was perceived that until some filtering mechanism is implemented, it is more suited for small systems.
...

It seems you have a wrong impression of what EMBEDDED in the kernel does.

Yes, I misunderstood it.

Thanks
Vivek

#5 lore raw
In reply to Vivek Goyal
Quoted 28 lines · Vivek Goyal
Quoted 10 lines · Adrian Bunk

config CRASH_DUMP
bool "kernel crash dumps (EXPERIMENTAL)" depends on EMBEDDED
depends on EXPERIMENTAL
depends on HIGHMEM
help
Generate crash dump after being started by kexec.

Two questions:
- If it has any dependencies on kexec, why isn't there a dependency?

crashdump has got dependency on kexec but not in the same kernel. What I mean is that as of today two kernels are involved in this process. First kernel is crashing kernel which should have enabled CONFIG_KEXEC and second kernel (capture kernel) is one which captures the dump and should have CONFIG_CRASH_DUMP enabled. Second kernel need not to have CONFIG_KEXEC enabled for catpturing dump. Hence CRASH_DUMP is not directly dependent on CONFIG_KEXEC.

Quoted 2 lines

- Is there any sane reason for the dependency on EMBEDDED?

I believe this was introduced because large servers can have huge amount of memory (running into Tera Bytes) and saving all that memory might not be practical. Hence it was perceived that until some filtering mechanism is implemented, it is more suited for small systems.

Quoted 5 lines

Personally I think it can be gotten away with because as a developer I can run gdb directly on /proc/vmcore and need not to save the whole memory hence need not to restrict this feature only for small systems.

Eric, do you think otherwise?

I would have to look again but I think the EMBEDDED dependency comes in more from the code that runs the kernel at a different address. But the essence is not because the crash dump kernel is for small systems (that isn't what embedded means anyway) but because at the moment you can't reasonably have the crash dump kernel be a general purpose kernel.

I have some patches which should use of a general purpose kernel. I need to find a few moments and get them into the -mm tree for further testing.

For most of the code under CONFIG_CRASH_DUMP my opinion is that all that is really need is fix /dev/mem to be usable, and we can do most if not all of the work in user space. But as long as we are communicating between the two kernels with a sane interface I really don't care.

Eric