[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1336481312.14207.164.camel@gandalf.stny.rr.com>
Date: Tue, 08 May 2012 08:48:32 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Oleg Nesterov <oleg@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Anton Arapov <anton@...hat.com>,
Stephen Boyd <sboyd@...eaurora.org>
Subject: Re: [PATCH v20] tracing: Fix kconfig warning due to a typo
On Tue, 2012-05-08 at 13:29 +0200, Peter Zijlstra wrote:
> On Tue, 2012-05-08 at 16:41 +0530, Srikar Dronamraju wrote:
> > + p:uprobes/p_zsh_0x46420 /bin/zsh:0x00046420 arg1=%ip arg2=%ax
>
> can you also do things like:
>
> p:uprobes/ponies /bin/zsh:foo arg1=bar
>
> when bar is either a function argument of foo (or an otherwise live
> variable at the probe point)?
>
> Only sampling register content is somewhat limiting, you might want to
> have %ax[5] + 24 for example, or a pure memory deref -- and the dwarves
> know where it all lives.
But this is for the raw entry into the kernel. The kernel wont know the
variable name. Although perf could do that parsing for you.
That said, the %ax[5] + 24 could be done in kernel, and that would be
useful. Does kprobes handle that?
-- Steve
--
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