[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160104211746.GD15669@kernel.org>
Date: Mon, 4 Jan 2016 18:17:46 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Jiri Olsa <jolsa@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Andi Kleen <andi@...stfloor.org>,
Wang Nan <wangnan0@...wei.com>
Subject: Re: [PATCHSET 00/10] perf tools: Support dynamic sort keys for
tracepoints (v3)
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 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