mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Anton Arapov <anton@redhat.com>,
	Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH v20] tracing: Fix kconfig warning due to a typo
Date: Tue, 08 May 2012 08:48:32 -0400	[thread overview]
Message-ID: <1336481312.14207.164.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1336476588.16236.20.camel@twins>

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



  reply	other threads:[~2012-05-08 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 11:11 Srikar Dronamraju
2012-05-08 11:29 ` Peter Zijlstra
2012-05-08 12:48   ` Steven Rostedt [this message]
2012-05-08 13:17     ` Peter Zijlstra
2012-05-09  5:55       ` Masami Hiramatsu
2012-05-09 10:57         ` Peter Zijlstra
2012-05-10 11:47           ` Masami Hiramatsu
2012-05-08 12:49 ` [tip:perf/uprobes] " tip-bot for Srikar Dronamraju

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=1336481312.14207.164.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=acme@infradead.org \
    --cc=ananth@in.ibm.com \
    --cc=anton@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sboyd@codeaurora.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®