Hi - > > While this does seem to be the right solution for the extant problem, I > > do want to take a moment and ask if the function sections need to be > > exposed at all? What tools use this information, and do they just want > > to see the bounds of the code region? (i.e. the start/end of all the > > .text* sections) Perhaps .text.* could be excluded from the sysfs > > section list? > [[cc += FChE, see [0] for Evgenii's full mail ]] Thanks! > It looks like debugging tools like systemtap [1], gdb [2] and its > add-symbol-file cmd, etc. peek at the /sys/module/<MOD>/section/ info. > But yeah, it would be preferable if we didn't export a long sysfs > representation if nobody actually needs it. Systemtap needs to know base addresses of loaded text & data sections, in order to perform relocation of probe point PCs and context data addresses. It uses /sys/module/...., kind of under protest, because there seems to exist no MODULE_EXPORT'd API to get at that information some other way. - FChE