From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv7 2.6.35-rc3-tip 11/11] perf: perf interface for uprobes
Date: Fri, 02 Jul 2010 20:25:17 +0900 [thread overview]
Message-ID: <4C2DCC9D.1020001@hitachi.com> (raw)
In-Reply-To: <4C2C2ECC.5060700@hitachi.com>
Masami Hiramatsu wrote:
> Srikar Dronamraju wrote:
>> perf: perf interface for uprobes
>>
>> Changelog from v4: Merged to 2.6.35-rc3-tip.
>>
>> Changelog from v3: (addressed comments from Masami Hiramatsu)
>> * Every process id has a different group name.
>> * event name starts with function name.
>> * If vaddr is specified, event name has vaddr appended
>> along with function name, (this is to avoid subsequent probes
>> using same event name.)
>> * warning if -p and --list options are used together.
>>
>> Also dso can either be a short name or absolute path.
>>
>> Enhances perf probe to accept pid and user vaddr.
>> Provides very basic support for uprobes.
>
> It's unsure what will happen if user sets a probe by line number...
> I'd like to suggest you if need_dwarf && uid, it should show an error message.
> But other parts are OK for me.
I've checked that perf probe was stopped by SEGV in convert_name_to_addr() with
below options.
# perf probe -u 2403 hoge.c:100
because pp->function == NULL.
Thank you,
--
Masami HIRAMATSU
2nd Research Dept.
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2010-07-02 11:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 18:34 [PATCHv7 2.6.35-rc3-tip 0/11] Uprobes Patches: Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 1/11] mm: Move replace_page() / write_protect_page() to mm/memory.c Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 2/11] uprobes: Breakpoint insertion/removal in user space applications Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 3/11] uprobes: Slot allocation for Execution out of line(XOL) Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 4/11] uprobes: x86 specific functions for user space breakpointing Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 5/11] uprobes: Uprobes (un)registration and exception handling Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 6/11] uprobes: X86 support for Uprobes Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 7/11] uprobes: Uprobes Documentation Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 8/11] trace: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 9/11] trace: uprobes trace_event interface Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 10/11] perf: Re-Add make_absolute_path Srikar Dronamraju
2010-06-29 18:37 ` [PATCHv7 2.6.35-rc3-tip 11/11] perf: perf interface for uprobes Srikar Dronamraju
2010-07-01 5:59 ` Masami Hiramatsu
2010-07-02 11:25 ` Masami Hiramatsu [this message]
2010-07-02 11:28 ` Srikar Dronamraju
2010-07-06 0:27 ` Masami Hiramatsu
2010-07-01 5:02 ` [PATCHv7 2.6.35-rc3-tip 0/11] Uprobes Patches: Srikar Dronamraju
2010-07-01 8:19 ` Ingo Molnar
2010-07-01 9:17 ` Masami Hiramatsu
2010-07-01 9:58 ` Ingo Molnar
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=4C2DCC9D.1020001@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=acme@infradead.org \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
/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