public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Hemant <hkshaw@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	linux-kernel@vger.kernel.org,        srikar@linux.vnet.ibm.com,
	peterz@infradead.org, oleg@redhat.com,
	       hegdevasant@linux.vnet.ibm.com, mingo@redhat.com,
	anton@redhat.com,        systemtap@sourceware.org,
	masami.hiramatsu.pt@hitachi.com,
	       aravinda@linux.vnet.ibm.com
Subject: Re: [PATCH v2 0/3] Perf support to SDT markers
Date: Tue, 08 Oct 2013 13:10:00 -0000	[thread overview]
Message-ID: <5254041D.70205@linux.vnet.ibm.com> (raw)
In-Reply-To: <874n8sku03.fsf@sejong.aot.lge.com>

On 10/08/2013 02:40 PM, Namhyung Kim wrote:
> Hi Frank,
>
> On Mon, 07 Oct 2013 11:47:09 -0400, Frank Ch. Eigler wrote:
>> Hemant Kumar <hkshaw@linux.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
>

Yes, it will be good to add this simpler example in the doc.

-- 
Thanks
Hemant

  reply	other threads:[~2013-10-08 13:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07  6:47 Hemant Kumar
2013-10-07  6:48 ` [PATCH v2 2/3] Support for perf to probe into SDT markers: Hemant Kumar
2013-10-08  9:09   ` Namhyung Kim
2013-10-08 13:09     ` Hemant
2013-10-08 11:47   ` Masami Hiramatsu
2013-10-08 13:30     ` Hemant
2013-10-07  6:48 ` [PATCH v2 1/3] SDT markers listing by perf: Hemant Kumar
2013-10-08  8:57   ` Namhyung Kim
2013-10-08 13:04     ` Hemant
2013-10-08 11:39   ` Masami Hiramatsu
2013-10-08 13:25     ` Hemant
2013-10-07  6:48 ` [PATCH v2 3/3] Documentation regarding perf/sdt Hemant Kumar
2013-10-07 15:48 ` [PATCH v2 0/3] Perf support to SDT markers Frank Ch. Eigler
2013-10-08  9:10   ` Namhyung Kim
2013-10-08 13:10     ` Hemant [this message]
2013-10-08 13:32   ` Hemant
2013-10-08  6:04 ` Masami Hiramatsu
2013-10-08 12:54   ` Hemant

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=5254041D.70205@linux.vnet.ibm.com \
    --to=hkshaw@linux.vnet.ibm.com \
    --cc=anton@redhat.com \
    --cc=aravinda@linux.vnet.ibm.com \
    --cc=fche@redhat.com \
    --cc=hegdevasant@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).