Messages in this thread | | | Date | Mon, 28 Oct 2013 10:56:04 +0200 | From | Pekka Enberg <> | Subject | Re: [PATCH v4 2/3] Support for perf to probe into SDT markers: |
| |
On 10/26/2013 12:50 PM, Ingo Molnar wrote: > I think in 99% of the usecases people will either use pre-built > markers that come with their distro, or will be intimately aware of > the markers because they are in the very app they are developing. > > So I wouldn't worry about 'user has a weird binary' case too much. > > I agree with Pekka that making them easily discoverable and visible > as a coherent whole is really important.
I wouldn't worry about the weird binary case either.
Even a build-time whitelist would help. Just put libc and libjvm there and you're already covering a lot of interesting cases. And if you then add a printout:
Use 'perf list --scan' to find more tracepoints on your system.
you're now effectively covering 100% of the cases.
The trick of making the UI not suck is not to force the user to think about the different mechanisms like SDT markers, uprobes, or ktap scripts but to make them as transparent as possible, provide useful defaults, and actively guide the user towards learning about more command line options for the complex cases.
Pekka
| |