patch for module function probe

[Frank Ch. Eigler]

Li Guanglei <guanglei@cn.ibm.com> writes:

> Actually, I think the expansion of module("*").function("foo") into
> kernel.function("foo") is a designed feature.

No, it was an accident.

> It is especially useful for those compiled-in kernel modules. [...]

Yes, it might be.  It would be best if there was a way of
automagically supporting module("foo") for a foo that's compiled into
vmlinux with a CONFIG_FOO=y instead of CONFIG_FOO=m.  Does kbuild
leave any traces of the module ancestry in object files produced this
way?


- FChE