From: Hemant <hkshaw@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: 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,
masami.hiramatsu.pt@hitachi.com,
Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] SDT markers listing by perf
Date: Wed, 04 Sep 2013 17:40:00 -0000 [thread overview]
Message-ID: <52277073.4090500@linux.vnet.ibm.com> (raw)
In-Reply-To: <87eh95t7cu.fsf@sejong.aot.lge.com>
On 09/04/2013 12:13 PM, Namhyung Kim wrote:
> On Tue, 03 Sep 2013 13:49:35 +0530, Hemant wrote:
>> On 09/03/2013 01:06 PM, Hemant Kumar wrote:
>>> This patch will enable perf to list all the sdt markers present
>>> in an elf file. The markers are present in the .note.stapsdt section
>>> of the elf. We can traverse through this section and collect the
>>> required info about the markers.
>>> This hasn't been thoroughly tested with the other
>>> options of perf.
>>> ----
>>> Usage :
>>> ./perf probe --list -x /lib64/libc.so.6
>> There is a mismatch between usage and the patch here. This should be:
>> perf probe --list -S /lib64/libc.so.6
> I guess it should be
>
> perf probe -S -x /lib64/libc.so.6
Yes, missed the -x option.
Thanks
Hemant
>
>
> Thanks,
> Namhyung
>
next prev parent reply other threads:[~2013-09-04 17:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 7:36 [RFC PATCH 0/2] Perf support to SDT markers Hemant Kumar Shaw
2013-09-03 7:37 ` [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 [this message]
2013-09-04 6:42 ` Namhyung Kim
2013-09-04 8:02 ` Masami Hiramatsu
2013-09-04 17:59 ` Hemant
2013-09-15 11:28 ` Hemant
2013-09-25 4:37 ` Masami Hiramatsu
2013-09-25 6:04 ` Hemant
2013-09-25 8:45 ` Masami Hiramatsu
2013-09-04 17:38 ` Hemant
2013-09-06 6:38 ` Namhyung Kim
2013-09-06 8:41 ` Hemant
2013-09-04 7:22 ` 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:22 ` Ingo Molnar
2013-09-03 15:12 ` Mark Wielaard
2013-09-03 19:24 ` Ingo Molnar
2013-09-03 15:24 ` Hemant
2013-09-04 6:49 ` Namhyung Kim
2013-09-04 8:23 ` Masami Hiramatsu
2013-09-04 8:26 ` 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:09 ` 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=52277073.4090500@linux.vnet.ibm.com \
--to=hkshaw@linux.vnet.ibm.com \
--cc=anton@redhat.com \
--cc=aravinda@linux.vnet.ibm.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).