From: Li Guanglei <guanglei@cn.ibm.com>
To: bibo mao <bibo_mao@linux.intel.com>
Cc: "Mao, Bibo" <bibo.mao@intel.com>,
systemtap <systemtap@sources.redhat.com>
Subject: Re: patch for module function probe
Date: Mon, 03 Apr 2006 10:03:00 -0000 [thread overview]
Message-ID: <4430F2F6.4010402@cn.ibm.com> (raw)
In-Reply-To: <4430E75E.5090204@linux.intel.com>
bibo mao :
> If it is designed feature, then kernel.function("foo") will be regarded
> as module("kernel").function("foo"). But if there is one module named
> "kernel.ko", how to probe its function although its module name is
> weird? In another way to say what is the meaning of
> module("kernel").function("foo"), else stap manual clarify that
> module("kernel") means kernel image, user had better not use the same
> module name.
I tried and found:
module("kernel").function("foo") == kernel.function("foo"), which
seems not appropriate.
I once thought module("*").function("foo") would be expanded as:
module("aaa").function("foo")
module("bbb").function("foo")
module("kernel").function("foo") // if happened to have a module
named module which also has a function named foo
...
kernel.function("foo")
That is to day, it should first search all loaded modules for function
foo, then at last it will also search kernel image for function foo.
So we need to change the current way it works with module("*").
next prev parent reply other threads:[~2006-04-03 10:03 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 [this message]
2006-04-03 16:14 ` Frank Ch. Eigler
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=4430F2F6.4010402@cn.ibm.com \
--to=guanglei@cn.ibm.com \
--cc=bibo.mao@intel.com \
--cc=bibo_mao@linux.intel.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).