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

From: Masami Hiramatsu
Date: Mon Oct 28 2013 - 07:23:54 EST

(2013/10/25 21:38), Pekka Enberg wrote:
> Hello Hemant,
> On Wed, Oct 23, 2013 at 7:05 AM, Hemant Kumar <hkshaw@xxxxxxxxxxxxxxxxxx> wrote:
>> This allows perf to probe into the sdt markers/notes present in
>> the libraries and executables. We try to find the associated location
>> and handle prelinking (since, stapsdt notes section is not allocated
>> during runtime). Prelinking is handled with the help of base
>> section which is allocated during runtime. This address can be compared
>> with the address retrieved from the notes' description. If its different,
>> we can take this difference and then add to the note's location.
>> We can use existing '-a/--add' option to add events for sdt markers.
>> Also, we can add multiple events at once using the same '-a' option.
>> Usage:
>> perf probe -x /lib64/ -a 'my_event=%libc:setjmp'
>> Output:
>> Added new event:
>> libc:my_event (on 0x35981)
>> 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?

By the way, what happens if multiple binaries has same SDT marker?
Yeah, perf list shows just one and ignores others. However, if we
probe one, and run binary which use the other one, user will never
see the marker.

So, it still needs a concrete binary path to list or, we should
support a syntax which specify actual binary, as like as below.

perf probe 'my_event=%libc:setjmp@/lib64/'

And perf list may show the marker as in same syntax (for copy&paste).

# perf list --sdt

Note that we need '%' to separate namespace :(, since user can define
any marker(provider) name in their binary...

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