public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Oleg Nesterov <oleg@redhat.com>, Mark Wielaard <mjw@redhat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Naren A Devaiah <naren.devaiah@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCHv8 2.6.35-rc4-tip 12/12]  perf: Show Potential probe points.
Date: Thu, 8 Jul 2010 16:20:57 -0400	[thread overview]
Message-ID: <20100708202057.GC30946@infradead.org> (raw)
In-Reply-To: <20100708171225.29165.28806.sendpatchset@localhost6.localdomain6>

> Show all potential probes in a process by pid 21106 across all dsos
> # perf probe -S -p 21106 | tail

Again, a file based interface would be much more useful.  E.g. what
possible probe points do I have in my qemu binary.

Btw, this doesn't mean I want to see the PID based variant removed, it
can be very useful for debugging long running processes.  I just don't
think it's the most important / conveniant one.

  reply	other threads:[~2010-07-08 20:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 17:10 [PATCHv8 2.6.35-rc4-tip 0/12] Uprobes Patches: Srikar Dronamraju
2010-07-08 17:10 ` [PATCHv8 2.6.35-rc4-tip 1/12] mm: Move replace_page() / write_protect_page() to mm/memory.c Srikar Dronamraju
2010-07-08 17:10 ` [PATCHv8 2.6.35-rc4-tip 2/12] uprobes: Breakpoint insertion/removal in user space applications Srikar Dronamraju
2010-07-08 17:10 ` [PATCHv8 2.6.35-rc4-tip 3/12] uprobes: Slot allocation for Execution out of line(XOL) Srikar Dronamraju
2010-07-08 17:10 ` [PATCHv8 2.6.35-rc4-tip 4/12] uprobes: x86 specific functions for user space breakpointing Srikar Dronamraju
2010-07-08 17:10 ` [PATCHv8 2.6.35-rc4-tip 5/12] uprobes: Uprobes (un)registration and exception handling Srikar Dronamraju
2010-07-08 17:11 ` [PATCHv8 2.6.35-rc4-tip 6/12] uprobes: X86 support for Uprobes Srikar Dronamraju
2010-07-08 17:11 ` [PATCHv8 2.6.35-rc4-tip 7/12] uprobes: Uprobes Documentation Srikar Dronamraju
2010-07-08 17:11 ` [PATCHv8 2.6.35-rc4-tip 8/12] trace: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju
2010-07-08 17:11 ` [PATCHv8 2.6.35-rc4-tip 9/12] trace: uprobes trace_event interface Srikar Dronamraju
2010-07-08 17:12 ` [PATCHv8 2.6.35-rc4-tip 10/12] perf: Re-Add make_absolute_path Srikar Dronamraju
2010-07-08 17:12 ` [PATCHv8 2.6.35-rc4-tip 11/12] perf: perf interface for uprobes Srikar Dronamraju
2010-07-08 20:19   ` Christoph Hellwig
2010-07-09  5:41     ` Srikar Dronamraju
2010-07-09  4:47   ` Srikar Dronamraju
2010-07-08 17:12 ` [PATCHv8 2.6.35-rc4-tip 12/12] perf: Show Potential probe points Srikar Dronamraju
2010-07-08 20:20   ` Christoph Hellwig [this message]
2010-07-09  5:56     ` Srikar Dronamraju
2010-07-09  7:17       ` Ingo Molnar
2010-07-09 14:13       ` Arnaldo Carvalho de Melo
2010-07-09  6:04   ` Srikar Dronamraju
2010-07-08 20:17 ` [PATCHv8 2.6.35-rc4-tip 0/12] Uprobes Patches: Christoph Hellwig
2010-07-09  4:42   ` 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=20100708202057.GC30946@infradead.org \
    --to=hch@infradead.org \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=mjw@redhat.com \
    --cc=naren.devaiah@in.ibm.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@xenotime.net \
    --cc=rostedt@goodmis.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