This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: patch for module function probe
- From: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
- To: "Roland McGrath" <roland at redhat dot com>, "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: <systemtap at sources dot redhat dot com>
- Date: Mon, 3 Apr 2006 14:47:54 -0700
- Subject: RE: patch for module function probe
Roland McGrath wrote:
>> 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?
>
> I don't think there is any way to recover that information.
Even if there were a way, this justs exacerbate the problem that started
this thread. If CONFIG_FOO=y and someone also compiles and loads an
unrelated module foo, which would you turn to for resolving
module("foo")?
Josh