From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Breno Leitao <leitao@linux.vnet.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: registration error (rc -22) on a standard function. Why ?
Date: Fri, 05 Dec 2008 11:51:00 -0000 [thread overview]
Message-ID: <20081205114909.GD7710@linux.vnet.ibm.com> (raw)
In-Reply-To: <49372A82.1030505@linux.vnet.ibm.com>
* Breno Leitao <leitao@linux.vnet.ibm.com> [2008-12-03 22:55:30]:
Hi Breno,
Can you if there are related messages in dmesg when you see this error?
-Srikar
> Hi,
>
> I am trying to probe a function which was static and inline. To probe
> it, I remove the static and inline modifier, to turn into a standard
> function, but now I am getting the following error:
>
> WARNING: probe module("bonding").function("_lock_tx_hashtbl@drivers/net/bonding/bond_alb.c:132") registration error (rc -22)
>
> Here is the function:
>
> void _lock_tx_hashtbl(struct bonding *bond)
> {
> spin_lock_bh(&(BOND_ALB_INFO(bond).tx_hashtbl_lock));
> }
>
> stap -p2 shows:
>
> module("bonding").function("_lock_tx_hashtbl@drivers/net/bonding/bond_alb.c:132") /* pc=.text+0x9b00 */ /* <- module("bonding").function("_lock_tx_hashtbl") */
>
>
> Objdump shows:
>
> 0000000000009b00 <._lock_tx_hashtbl>:
> 9b00: 7c 08 02 a6 mflr r0
> 9b04: 38 63 01 f0 addi r3,r3,496
> 9b08: f8 01 00 10 std r0,16(r1)
> 9b0c: f8 21 ff 91 stdu r1,-112(r1)
> 9b10: 48 00 00 01 bl 9b10 <._lock_tx_hashtbl+0x10>
> 9b10: R_PPC64_REL24 ._spin_lock_bh
> 9b14: 60 00 00 00 nop
> 9b18: 38 21 00 70 addi r1,r1,112
> 9b1c: e8 01 00 10 ld r0,16(r1)
> 9b20: 7c 08 03 a6 mtlr r0
> 9b24: 4e 80 00 20 blr
>
>
> I really didn't understand why I can't probe that function. Any idea
> what might be wrong ?
>
> Thanks
> Breno
prev parent reply other threads:[~2008-12-05 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 0:56 Breno Leitao
2008-12-04 3:41 ` Ananth N Mavinakayanahalli
2008-12-04 18:52 ` Frank Ch. Eigler
2008-12-05 11:51 ` Srikar Dronamraju [this message]
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=20081205114909.GD7710@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=leitao@linux.vnet.ibm.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).