Re: [PATCHv8 2.6.35-rc4-tip 12/12] perf: Show Potential probepoints.

[Ingo Molnar]

* Srikar Dronamraju <srikar@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/