From: fche@redhat.com (Frank Ch. Eigler)
To: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: William Cohen <wcohen@redhat.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: perf software events broken in containers
Date: Mon, 27 Mar 2017 12:10:14 -0400 [thread overview]
Message-ID: <y0mpoh2og49.fsf@fche.csb> (raw)
In-Reply-To: <CAE40pdd06QXckEMYfU63c=Zvrrn22A-sm-Sh37CymR5rpJZ57Q@mail.gmail.com> (Brendan Gregg's message of "Wed, 22 Mar 2017 12:59:22 -0700")
brendan.d.gregg wrote:
> [...]
>> stap -v -e 'probe kernel.function("idr_find").return {printf("%s %s 0x%x\n", pn(), $$parms$, $return)}'
>>
>
> Right, I've been doing that with ftrace/kprobes/bcc/BPF... Many of the
> functions aren't visible, though, I suspect inlined.
stap is comfortable with probing inlined functions, or
generally any statements within functions.
See e.g. https://sourceware.org/systemtap/examples/#general/whythefail.stp
- FChE
prev parent reply other threads:[~2017-03-27 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 18:24 perf software events broken in containers Brendan Gregg
2017-03-22 19:15 ` William Cohen
2017-03-22 19:59 ` Brendan Gregg
2017-03-22 20:29 ` William Cohen
2017-03-22 21:35 ` Brendan Gregg
2017-03-23 14:21 ` David Ahern
2017-03-27 16:10 ` Frank Ch. Eigler [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=y0mpoh2og49.fsf@fche.csb \
--to=fche@redhat.com \
--cc=brendan.d.gregg@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=wcohen@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 NNTP newsgroup(s).