public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: voyager1983 <wang.yongzhi2009@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: Can kernel.statement access the function argument?
Date: Mon, 11 Apr 2011 17:40:00 -0000	[thread overview]
Message-ID: <y0mwrj0ivbv.fsf@fche.csb> (raw)
In-Reply-To: <31356706.post@talk.nabble.com> (wang.yongzhi2009@gmail.com's message of "Fri, 8 Apr 2011 17:37:34 -0700 (PDT)")

voyager1983 <wang.yongzhi2009@gmail.com> writes:

> What I am about to probe is actually the statement   
> ret = action->handler(irq, action->dev_id);
> [...]
> stap -L 'kernel.statement("handle_IRQ_event@kernel/irq/handle.c:376")'
> It returns nothing.

That's partly because the handle_IRQ_event function is blacklisted due
to some historical incompatibility with kernel kprobes.  You may try
again with stap -g ...

- FChE

  reply	other threads:[~2011-04-11 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08  3:52 voyager1983
2011-04-08 15:51 ` William Cohen
2011-04-09  0:37   ` voyager1983
2011-04-11 17:40     ` Frank Ch. Eigler [this message]
2011-04-20 12:34       ` voyager1983

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=y0mwrj0ivbv.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=systemtap@sourceware.org \
    --cc=wang.yongzhi2009@gmail.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).