lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100709071751.GC10743@elte.hu>
Date:	Fri, 9 Jul 2010 09:17:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Randy Dunlap <rdunlap@...otime.net>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Mark Wielaard <mjw@...hat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Naren A Devaiah <naren.devaiah@...ibm.com>,
	Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCHv8 2.6.35-rc4-tip 12/12]  perf: Show Potential probe
 points.


* Srikar Dronamraju <srikar@...ux.vnet.ibm.com> wrote:

> 
> > > 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.
> 
> Right, Currently perf probe needs -p option because it depend on
> thread->map_groups for listing the dsos and its functions.
> 
> I am not sure if perf already has ability to list functions in a file esp if 
> we dont have dwarf information in that file. If perf has the ability I will 
> reuse it here or will try implementing one.

Excellent - this would increase usability very visibly.

People fundamentally like to work in the ASCII space: command names, function 
names, etc. People like to query these spaces to figure out what's available 
and use wildcards to define categories or limit queries.

PIDs and addresses are useful too - but it's mostly for computers or for 
odd-one-out cases: tools and the occasional need-something-on-the-PID-level 
lowlevel workflow.

Thanks,

	Ingo
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ