On Wed, Jul 15, 2015 at 06:15:37PM +0900, Masami Hiramatsu wrote:
> perf buildid-cache --add <binary> scans given binary and add
> the SDT events to probe cache. It is possible to use the cached
> SDT events as other cached events (perf probe <provider>:<event>=<event>).

That means lookup the cached SDT events only using event name, right?
What if same event names are used by more than one providers?


> 
> e.g.
>   ----
>   # perf buildid-cache --add /lib/libc-2.17.so
>   # perf probe --cache --list | head -n 5
>   /usr/lib/libc-2.17.so (a6fb821bdf53660eb2c29f778757aef294d3d392):
>   libc:setjmp=setjmp
>   libc:longjmp=longjmp
>   libc:longjmp_target=longjmp_target
>   libc:memory_heap_new=memory_heap_new

I expected something like this instead..

    libc:memory_heap_new=new_heap+183


Thanks,
Namhyung


>   # perf probe -x /usr/lib/libc-2.17.so \
>     -a libc:memory_heap_new=memory_heap_new
>   Added new event:
>     libc:memory_heap_new (on memory_heap_new
>    in /usr/lib/libc-2.17.so)
> 
>   You can now use it in all perf tools, such as:
> 
>           perf record -e libc:memory_heap_new -aR sleep 1
> 
>   # perf probe -l
>     libc:memory_heap_new (on new_heap+183 in /usr/lib/libc-2.17.so)
>   ----
> 
> Note that SDT event entries in probe-cache file is somewhat different
> from normal cached events. Normal one starts with "#", but SDTs are
> starting with "%".
> 
> Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>