From: Mark Wielaard <mjw@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Hemant <hkshaw@linux.vnet.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-kernel@vger.kernel.org, srikar@linux.vnet.ibm.com,
peterz@infradead.org, oleg@redhat.com, mingo@redhat.com,
anton@redhat.com, systemtap@sourceware.org
Subject: Re: [RFC PATCH 0/2] Perf support to SDT markers
Date: Tue, 03 Sep 2013 17:11:02 +0200 [thread overview]
Message-ID: <1378221062.3948.86.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <20130903142159.GA27740@gmail.com>
On Tue, 2013-09-03 at 16:21 +0200, Ingo Molnar wrote:
> * Hemant <hkshaw@linux.vnet.ibm.com> wrote:
>
> > Here is an overview and a high-level-description:
>
> Thanks, looks like a pretty useful feature - especially if SDT probes are
> already widely present in various server binaries on a typical Linux
> distro (are they?).
They are becoming fairly common, especially now that glibc has adopted
them. And they were designed to be source compatible with DTRACE markers
[*]. So any program that has probes for dtrace can just be recompiled on
with sys/sdt.h to get them.
My Fedora 19 box already has a couple of applications and libraries
installed that support them:
$ stap -l 'process("/usr/*/*").mark("*")' | cut -f2 -d\" | uniq -c
9 /usr/bin/Xorg
9 /usr/bin/Xvfb
4 /usr/bin/c++
4 /usr/bin/cpp
4 /usr/bin/g++
4 /usr/bin/gcc
1 /usr/bin/gcov
4 /usr/bin/gfortran
3 /usr/bin/qemu-ga
75 /usr/bin/qemu-img
75 /usr/bin/qemu-io
75 /usr/bin/qemu-nbd
575 /usr/bin/qemu-system-i386
575 /usr/bin/qemu-system-x86_64
29 /usr/bin/stap
3 /usr/bin/stapdyn
3 /usr/bin/virtfs-proxy-helper
4 /usr/bin/x86_64-redhat-linux-c++
4 /usr/bin/x86_64-redhat-linux-g++
4 /usr/bin/x86_64-redhat-linux-gcc
13 /usr/lib/ld-2.17.so
1 /usr/lib/libanl-2.17.so
5 /usr/lib/libc-2.17.so
1 /usr/lib/libgcc_s-4.8.1-20130603.so.1
22 /usr/lib/libpthread-2.17.so
1 /usr/lib/librt-2.17.so
3 /usr/lib/libstdc++.so.6.0.18
13 /usr/lib64/ld-2.17.so
1 /usr/lib64/libanl-2.17.so
5 /usr/lib64/libc-2.17.so
3 /usr/lib64/libcacard.so.0.0.0
1 /usr/lib64/libgcc_s-4.8.1-20130603.so.1
6 /usr/lib64/libglib-2.0.so.0.3600.3
11 /usr/lib64/libgobject-2.0.so.0.3600.3
4 /usr/lib64/libm-2.17.so
23 /usr/lib64/libpthread-2.17.so
2 /usr/lib64/libpython2.7.so.1.0
2 /usr/lib64/libpython3.3m.so.1.0
1 /usr/lib64/librt-2.17.so
3 /usr/lib64/libstdc++.so.6.0.18
15 /usr/lib64/libtcl8.5.so
41 /usr/lib64/libvirt.so.0.1000.5
37 /usr/libexec/libvirt_lxc
12 /usr/sbin/ldconfig
3 /usr/sbin/libvirtd
34 /usr/sbin/prelink
12 /usr/sbin/sln
37 /usr/sbin/virtlockd
[*] http://tromey.com/blog/?p=687
next prev parent reply other threads:[~2013-09-03 15:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 7:36 Hemant Kumar Shaw
2013-09-03 7:36 ` [PATCH 1/2] SDT markers listing by perf Hemant Kumar
2013-09-03 8:19 ` Hemant
2013-09-04 6:43 ` Namhyung Kim
2013-09-04 17:40 ` Hemant
2013-09-04 6:42 ` Namhyung Kim
2013-09-04 8:01 ` Masami Hiramatsu
2013-09-04 17:58 ` Hemant
2013-09-15 11:28 ` Hemant
2013-09-25 4:37 ` Masami Hiramatsu
2013-09-25 6:03 ` Hemant
2013-09-25 8:45 ` Masami Hiramatsu
2013-09-04 17:37 ` Hemant
2013-09-06 6:37 ` Namhyung Kim
2013-09-06 8:41 ` Hemant
2013-09-04 7:21 ` Masami Hiramatsu
2013-09-04 17:52 ` Hemant
2013-09-03 7:37 ` [PATCH 2/2] Support to perf to probe on SDT markers: Hemant Kumar
2013-09-03 9:14 ` Masami Hiramatsu
2013-09-04 7:00 ` Namhyung Kim
2013-09-04 8:10 ` Masami Hiramatsu
2013-09-04 18:00 ` Hemant
2013-09-04 17:50 ` Hemant
2013-09-03 8:25 ` [RFC PATCH 0/2] Perf support to SDT markers Ingo Molnar
2013-09-03 9:17 ` Masami Hiramatsu
2013-09-03 13:23 ` Hemant
2013-09-03 14:21 ` Ingo Molnar
2013-09-03 15:11 ` Mark Wielaard [this message]
2013-09-03 19:24 ` Ingo Molnar
2013-09-03 15:24 ` Hemant
2013-09-04 6:49 ` Namhyung Kim
2013-09-04 8:22 ` Masami Hiramatsu
2013-09-04 8:25 ` Mark Wielaard
2013-09-04 8:39 ` Masami Hiramatsu
2013-09-04 18:08 ` Hemant
2013-09-05 4:59 ` Masami Hiramatsu
2013-09-04 18:12 ` Hemant
2013-09-04 18:52 ` Mark Wielaard
2013-09-04 20:39 ` Hemant
2013-09-04 17:45 ` Hemant
2013-09-04 6:08 ` Namhyung Kim
2013-09-04 17:08 ` Hemant
2013-09-04 23:41 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378221062.3948.86.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=anton@redhat.com \
--cc=hkshaw@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®