Re: [perfmon2] [PATCH] perf: make perf report -D print sampled CPU

[Arnaldo C. de M. <ac...@in...>]

Em Fri, May 28, 2010 at 03:44:31PM +0200, Stephane Eranian escreveu:
> On Fri, May 28, 2010 at 3:37 PM, Arnaldo Carvalho de Melo
> <ac...@in...> wrote:
> > Em Fri, May 28, 2010 at 03:03:15PM +0200, Stephane Eranian escreveu:
> >> On Fri, May 28, 2010 at 2:57 PM, Arnaldo Carvalho de Melo
> >> <ac...@in...> wrote:
> >> > Em Fri, May 28, 2010 at 12:08:01PM +0200, Stephane Eranian escreveu:
> >> Fine. I think there needs to be some documenation explaining the structure
> >> of the line here. I had to dig into the code to understand it.
> >
> > Right, this so far is as ad-hoc as it can be :-)
> >
> > One idea that is in my TODO list is to generate some XML format people
> > say that oprofile produces and there is also some other format that a
> > valgrind tool uses that should be supported.

> I think for a lot of people what matter is that the format be easily parseable
> by Python/Perl scripts. XML may be fine too.

Agreed, I mentioned the existing formats because they may be good enough
and would allow us to take advantage of existing tools that process
them.
 
> > I also plan to have it in a spreadsheet TUI widget, allowing lots of
> > navigation gimmicks to help in debugging, like a popup that offers
> > the list of mmaps for the thread where the sample below the cursor
> > happened, etc.

> You may get tons of data. Not sure you could manage interactively.

Right, it wouldn't support all cases, but I'm working on new TUI widgets
that try hard not to create several layers of data structures to browse
the perf.data file, i.e. filtering shouldn't traverse all the entries,
just set variables that will be inspected when we move to a different
page, etc.

- Arnaldo