linux-kernel - Re: [PATCH v2 0/3] 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]

Date:	Tue, 08 Oct 2013 18:10:52 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	fche@...hat.com (Frank Ch. Eigler)
Cc:	Hemant Kumar <hkshaw@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, srikar@...ux.vnet.ibm.com,
	peterz@...radead.org, oleg@...hat.com,
	hegdevasant@...ux.vnet.ibm.com, mingo@...hat.com, anton@...hat.com,
	systemtap@...rceware.org, masami.hiramatsu.pt@...achi.com,
	aravinda@...ux.vnet.ibm.com
Subject: Re: [PATCH v2 0/3] Perf support to SDT markers

Hi Frank,

On Mon, 07 Oct 2013 11:47:09 -0400, Frank Ch. Eigler wrote:
> Hemant Kumar <hkshaw@...ux.vnet.ibm.com> writes:
>
>> [...]
>> A simple example to show this follows.
>> - Create a file with .d extension and mention the probe names in it with
>> provider name and marker name.
>> [...]
>> - Now create the probes.h and probes.o file :
>> $ dtrace -C -h -s probes.d -o probes.h
>> $ dtrace -C -G -s probes.d -o probes.o
>> [...]
>
> It may be worthwhile to document an even-simpler case:
>
> - no .d file
> - no invocation of the dtrace python script
> - no generated .h or .o file
> - in the C file, just add:
>
>   #include <sys/sdt.h>
>
>   void main () {
>        /* ... */
>        STAP_PROBE(provider_name,probe_name);
>        /* ... */
>   }
>
> - gcc file.c
> - stap -l 'process("./a.out").mark("*")' to list

Yes, looks much simpler and better.

Hemant, would you add it to the doc too?

Thanks,
Namhyung
--
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/