Em Mon, Dec 21, 2015 at 11:26:43PM +0900, Namhyung Kim escreveu:
> Hello,
>
> This is an attempt to improve perf to deal with tracepoint events
> better. The perf tools can handle tracepoint events but perf report
> on them is less useful since they're always sampled in a fixed
> location and not provide event specific info. We can use perf script
> but I always wishes there's more convenient way to see the result.
>
> * changes in v3)
> - save trace_output for dynamic entries (Jiri)
> - update field length for each entry
Thanks, applied, I made a few changes, related to libtraceevent function
names, split a patch in two, please take a look at my perf/core branch,
should all be ok.
Ah, please consider looking for field names directly, i.e. make this
work for a kmem:kmalloc event:
perf report -s comm,gfp_flags
:-)
I think this can get mapped even when multiple events are available,
i.e. use that for the events that have such a field.
It could even get more relaxed, like:
perf report -s comm,flags
No?
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
