[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100825065541.GE14431@linux.vnet.ibm.com>
Date: Wed, 25 Aug 2010 12:25:41 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: Arnaldo Carvalho de Melo <acme@...radead.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Steven Rostedt <rostedt@...dmis.org>,
Fr?d?ric Weisbecker <fweisbec@...il.com>,
2nddept-manager@....hitachi.co.jp, Ingo Molnar <mingo@...e.hu>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Using perf probe with arguments throws a fatal error.
> >
> > 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
--
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/
Powered by blists - more mailing lists