Hello, Jeff Mahoney wrote:
I was primarily thinking about percpu areas - how percpu areas are setup and accessed differently on some archs (s390 specifically) and the vmlinux defined symbols which need to be changed if the percpu sections are merged and so on. My worries could be bogus but things are subtle. I think it would be better if we can somehow share the usual module loading code path while skipping time consuming stages.
If this were a problem, wouldn't we be running into subtle bugs already? The .o files already have the .data.percpu sections regardless of whether it's a module or not. The only special case seems to be that the module code has to parse the percpu section itself and the static kernel uses global variables to delimit the sections.
Regardless, I don't think we're really targeting s/390 with this. Really, we're only interested in the x86-based arches.
Hmmm... yeah, now that I think more about it, it should be okay for x86 and for other archs too if the symbols are adjusted properly and all. Thanks. -- tejun -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org