From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Fr?d?ric Weisbecker <fweisbec@gmail.com>,
2nddept-manager@sdl.hitachi.co.jp, Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Using perf probe with arguments throws a fatal error.
Date: Wed, 25 Aug 2010 12:25:41 +0530 [thread overview]
Message-ID: <20100825065541.GE14431@linux.vnet.ibm.com> (raw)
In-Reply-To: <4C74AE7B.1010705@hitachi.com>
> >
> > The differences I see when a name is given we refer the name, while in
> > the previous case we refer the register %ip.
>
> Ah, I remembered that, yeah, perf doesn't support those raw regsiters,
> dereferences, etc.
> Hmm, this should be solved, but not so simple as just removing "%",
> because there are also special variables ($retval, $stack) and
> dereferences(+8(+10(%sp)), etc).
>
> I think the simplest solution is just setting "argX" name for each
> argument (if user omitted its name) in kprobe-tracer (because
> trace-cmd will face same problem).
> e.g.
> # echo "p do_fork %ip" > tracing/kprobe_events
> will be translated as below
> # echo "p do_fork arg1=%ip" > tracing/kprobe_events
>
Okay, I will follow the same and fix the argX name in uprobe-tracer.
--
Thanks and Regards
Srikar
prev parent reply other threads:[~2010-08-25 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100824045758.GA14431@linux.vnet.ibm.com>
[not found] ` <4C738411.8080602@hitachi.com>
[not found] ` <20100824085401.GB14431@linux.vnet.ibm.com>
[not found] ` <4C738F09.3080108@hitachi.com>
[not found] ` <20100824095658.GC14431@linux.vnet.ibm.com>
2010-08-25 5:47 ` Using perf probe with arguments throws a fatal error Masami Hiramatsu
2010-08-25 6:55 ` Srikar Dronamraju [this message]
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=20100825065541.GE14431@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=acme@infradead.org \
--cc=ananth@in.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.