linux-kernel - Re: [RFC PATCH 0/2] Perf support to SDT markers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130903192411.GA2403@gmail.com>
Date:	Tue, 3 Sep 2013 21:24:11 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Mark Wielaard <mjw@...hat.com>
Cc:	Hemant <hkshaw@...ux.vnet.ibm.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	linux-kernel@...r.kernel.org, srikar@...ux.vnet.ibm.com,
	peterz@...radead.org, oleg@...hat.com, mingo@...hat.com,
	anton@...hat.com, systemtap@...rceware.org
Subject: Re: [RFC PATCH 0/2] Perf support to SDT markers


* Mark Wielaard <mjw@...hat.com> wrote:

> On Tue, 2013-09-03 at 16:21 +0200, Ingo Molnar wrote:
> > * Hemant <hkshaw@...ux.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

Nice!

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/