This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [RFC PATCH 0/2] Perf support to SDT markers
- From: Ingo Molnar <mingo at kernel dot org>
- To: Hemant Kumar Shaw <hkshaw at linux dot vnet dot ibm dot com>
- Cc: linux-kernel at vger dot kernel dot org, srikar at linux dot vnet dot ibm dot com, peterz at infradead dot org, oleg at redhat dot com, mingo at redhat dot com, anton at redhat dot com, systemtap at sourceware dot org, masami dot hiramatsu dot pt at hitachi dot com
- Date: Tue, 3 Sep 2013 10:25:03 +0200
- Subject: Re: [RFC PATCH 0/2] Perf support to SDT markers
- Authentication-results: sourceware.org; auth=none
- References: <20130903072944 dot 4793 dot 93584 dot stgit at hemant-fedora>
* Hemant Kumar Shaw <hkshaw@linux.vnet.ibm.com> wrote:
> This series adds support to perf to list and probe into the SDT markers.
> The first patch implements listing of all the SDT markers present in
> the ELFs (executables or libraries). The SDT markers are present in the
> .note.stapsdt section of the elf. That section can be traversed to list
> all the markers. Recognition of markers follows the SystemTap approach.
>
> The second patch will allow perf to probe into these markers. This is
> done by writing the marker name and its offset into the
> uprobe_events file in the tracing directory.
> Then, perf tools can be used to analyze perf.data file.
Please provide a better high level description that explains the history
and scope of SDT markers, how SDT markers get into binaries, how they can
be used for probing, a real-life usage example that shows something
interesting not possible via other ways, etc.
Thanks,
Ingo