Re: Re: [PATCH v4 2/3] Support for perf to probe into SDT markers:

From: Masami Hiramatsu
Date: Mon Oct 28 2013 - 06:57:54 EST

(2013/10/26 18:50), Ingo Molnar wrote:
> * Srikar Dronamraju <srikar@xxxxxxxxxxxxxxxxxx> wrote:
>> Hi Pekka,
>>>> You can now use it in all perf tools, such as:
>>>> perf record -e libc:my_event -aR sleep 1
>>> Is there a technical reason why 'perf list' could not show all the
>>> available SDT markers on a system and that the 'market to event'
>>> mapping cannot happen automatically?
>> Technically feasible. But then we would have to parse each of the
>> libraries and executables to list them. Right? I am not sure if
>> such a delay is acceptable.
> I'd say lets try Pekka's suggestion and make it more palatable if
> there's complaints about the delay. (SSD systems are becoming
> dominant and there the search should be reasonably fast.)
> We could also make 'perf list' more sophisticated, if invoked
> naively as 'perf list' then maybe it should first display the
> various event categories, with a (rough) count:
> $ perf list
> 34 hardware events # use 'perf list --hw' to list them
> 40 hw-cache events # use 'perf list --cache' to list them
> 20 software events # use 'perf list --sw' to list them
> 2 raw events # use 'perf list --raw' to list them
> 120 tracepoints # use 'perf list --tp' to list them
> >10 SDT tracepoints # use 'perf list --sdt' to list them
> # use 'perf list -a' to list all events
> # use 'perf list ./binary' to list events in a given binary
> I.e. bring a bit more structure into it.

Ah, that's nice to me too ;)

Thank you,

IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at