[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140424210015.GJ8488@redhat.com>
Date: Thu, 24 Apr 2014 17:00:15 -0400
From: Don Zickus <dzickus@...hat.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCHSET 00/17] perf report: Add -F option for specifying
output fields (v4)
On Thu, Apr 24, 2014 at 10:41:39PM +0900, Namhyung Kim wrote:
> Hi Don,
>
> 2014-04-23 (수), 08:58 -0400, Don Zickus:
> > On Wed, Apr 23, 2014 at 03:15:35PM +0900, Namhyung Kim wrote:
> > > On Tue, 22 Apr 2014 17:16:47 -0400, Don Zickus wrote:
> > > > ./perf mem record -a grep -r foo /* > /dev/null
> > > > ./perf mem report -F overhead,symbol_daddr,pid -s symbol_daddr,pid --stdio
> > > >
> > > > I was thinking I could sort everything based on the symbol_daddr and pid.
> > > > Then re-sort the output to display the highest 'symbol_daddr,pid' pair.
> > > > But it didn't seem to work that way. Instead it seems like I get the
> > > > original sort just displayed in the -F format.
> > >
> > > Could you please show me the output of your example?
> >
> >
> > # To display the perf.data header info, please use --header/--header-only
> > # options.
> > #
> > # Samples: 96K of event 'cpu/mem-loads/pp'
> > # Total weight : 1102938
> > # Sort order : symbol_daddr,pid
> > #
> > # Overhead Data Symbol Command: Pid
> > # ........ ......................................................................
> > #
> > 0.00% [k] 0xffff8807a8c1cf80 grep:116437
> > 0.00% [k] 0xffff8807a8c8cee0 grep:116437
> > 0.00% [k] 0xffff8807a8dceea0 grep:116437
> > 0.01% [k] 0xffff8807a9298dc0 grep:116437
> > 0.01% [k] 0xffff8807a934be40 grep:116437
> > 0.00% [k] 0xffff8807a9416ec0 grep:116437
> > 0.02% [k] 0xffff8807a9735700 grep:116437
> > 0.00% [k] 0xffff8807a98e9460 grep:116437
> > 0.02% [k] 0xffff8807a9afc890 grep:116437
> > 0.00% [k] 0xffff8807aa64feb0 grep:116437
> > 0.02% [k] 0xffff8807aa6b0030 grep:116437
>
> Hmm.. it seems that it's exactly sorted by the data symbol addresses, so
> I don't see any problem here. What did you expect? If you want to see
> those symbol_daddr,pid pair to be sorted by overhead, you can use the
> one of -F or -s option only.
Good question. I guess I was hoping to see things sorted by overhead, but
as you said removing all the -F options gives me that. I have been
distracted with other fires this week, I lost focus at what I was trying
to accomplish.
Let me figure that out again and try to come up with a more clear email
explaining what I was looking for (for myself at least :-) ).
Sorry for the distraction.
Cheers,
Don
--
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