diff options
author | Srinivasa Ds <srinivasa@in.ibm.com> | 2007-04-23 11:28:49 +0530 |
---|---|---|
committer | Paul Mackerras <paulus@samba.org> | 2007-05-02 20:04:32 +1000 |
commit | eb609e52d188775da738a1ffd1e982e6212c77d7 (patch) | |
tree | c3fdca2f59b661210f7b44ddf6efc6c65ee16e86 /ipc | |
parent | 14d1d2f25bca1c4ed45704c8019f6c971c40bba4 (diff) | |
download | linux-eb609e52d188775da738a1ffd1e982e6212c77d7.tar.gz linux-eb609e52d188775da738a1ffd1e982e6212c77d7.tar.bz2 linux-eb609e52d188775da738a1ffd1e982e6212c77d7.zip |
[POWERPC] Transparently handle <.symbol> lookup for kprobes
When data symbols are not present in kernel image, user needs to add
dot(".") before function name explicitly, that he wants to probe in kprobe
module on ppc64.
for ex:-
When data symbols are missing on ppc64,
====================
[root@llm27lp1 ~]# cat /proc/kallsyms | grep do_fork
c00000000006283c T .do_fork
==============================
User needs add "." to "do_fork"
kp.symbol_name = ".do_fork";
============================
This makes kprobe modules unportable. This fixes the problem.
Signed-off-by: Srinivasa Ds <srinivasa@in.ibm.com>
Signed-off-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions