[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131028103402.GB6274@gmail.com>
Date: Mon, 28 Oct 2013 11:34:02 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Pekka Enberg <penberg@....fi>
Cc: "Frank Ch. Eigler" <fche@...hat.com>,
Pekka Enberg <penberg@...nel.org>,
Hemant Kumar <hkshaw@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Oleg Nesterov <oleg@...hat.com>,
hegdevasant@...ux.vnet.ibm.com, Ingo Molnar <mingo@...hat.com>,
anton@...hat.com, systemtap@...rceware.org,
Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
aravinda@...ux.vnet.ibm.com
Subject: Re: [PATCH v4 2/3] Support for perf to probe into SDT markers:
* Pekka Enberg <penberg@....fi> wrote:
> On 10/26/2013 02:16 PM, Frank Ch. Eigler wrote:
> >Pekka Enberg <penberg@...nel.org> writes:
> >
> >>Is there a technical reason why 'perf list' could not show all the
> >>available SDT markers on a system and that the 'mark to event'
> >>mapping cannot happen automatically? [...]
> >A quick experiment with:
> >
> > find `echo $PATH | tr : ' '` -type f -perm -555 |
> > xargs readelf -n 2>/dev/null |
> > grep STAP 2>/dev/null
> >
> >suggests reasonable performance for my F19 workstation (a second or
> >two over ~6000 executables), once all the ELF content is in the block
> >cache. According to a stap eventcount.stp run, that required about
> >50000 syscall.read events.
> >
> >Note that a $PATH search excludes shared libraries, which can also
> >carry <sys/sdt.h> markers. Adding /usr/lib* in more than doubles the
> >work, then there's /usr/libexec etc.
>
> Thanks for providing numbers to the discussion. AFAICT, we might
> even be able to just scan everything for 'perf list' by default.
That should definitely be better in the long run than any whitelist
(or no list at all).
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists