I'm getting reports of some people ending up with 1GB piggy objects for
gzip to compress on ARM. While investigating this, I found the following:
00003dd4 ? __module_kernel_version
00003df4 ? __module_parm_minor
00003e04 ? __module_parm_flash_base
00003e18 ? __module_parm_flash_size
40004000 A swapper_pg_dir
40008000 ? __init_begin
40008000 ? _stext
40008000 ? stext
The __module_* stuff is from the .modinfo section of some kernel object.
Since .modinfo isn't actually used or indeed placed in the linker
script, shouldn't we be explicitly discarding it like the
.exitcall.exit, .text.exit and .data.exit sections, rather than
letting the linker apparantly pick some random memory location to
dump this section?
(Yes, its probably buggy for the linker not to moan about unrecognised
input sections...)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/