From mboxrd@z Thu Jan 1 00:00:00 1970 From: fche@redhat.com (Frank Ch. Eigler) Subject: Re: perf software events broken in containers Date: Mon, 27 Mar 2017 12:10:14 -0400 Message-ID: References: <8c4186d0-bfbf-6f1a-c953-9859bf057856@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com ([209.132.183.28]:60398 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751124AbdC0QKQ (ORCPT ); Mon, 27 Mar 2017 12:10:16 -0400 In-Reply-To: (Brendan Gregg's message of "Wed, 22 Mar 2017 12:59:22 -0700") Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Brendan Gregg Cc: William Cohen , "linux-perf-use." 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