From: fche@redhat.com (Frank Ch. Eigler)
To: systemtap@sources.redhat.com
Subject: Re: patch for module function probe
Date: Mon, 03 Apr 2006 16:14:00 -0000 [thread overview]
Message-ID: <y0mfykubpqv.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <4430E569.8050904@cn.ibm.com>
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
next prev parent reply other threads:[~2006-04-03 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 8:56 Mao, Bibo
2006-04-03 9:06 ` Li Guanglei
2006-04-03 9:24 ` bibo mao
2006-04-03 10:03 ` Li Guanglei
2006-04-03 16:14 ` Frank Ch. Eigler [this message]
2006-04-03 19:16 ` Roland McGrath
2006-04-03 21:47 Stone, Joshua I
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y0mfykubpqv.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).