linux-kernel - Re: [PATCHSET 00/17] perf report: Add -F option for specifying output fields (v4)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 23 Apr 2014 08:58:28 -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 Wed, Apr 23, 2014 at 03:15:35PM +0900, Namhyung Kim wrote:
> Hi Don,
> 
> On Tue, 22 Apr 2014 17:16:47 -0400, Don Zickus wrote:
> > On Wed, Apr 16, 2014 at 12:05:37PM +0900, Namhyung Kim wrote:
> >> Hello,
> >> 
> >> This is a patchset implementing -F/--fields option to setup output
> >> field/column as Ingo requested.  It depends on my --percentage
> >> patchset [1].
> >> 
> >> The -F option can receive any sort keys that -s option recognize, plus
> >> following fields (name can be changed):
> >> 
> >>   overhead, overhead_sys, overhead_us, sample, period
> >> 
> >> The overhead_guest_sys and overhead_guest_us might be avaiable when
> >> you profile guest machines.
> >> 
> >> Output will be sorted by in order of fields and sort keys passed by -s
> >> option will be added to the output field list automatically.  If you
> >> want to change the order of sorting you can give -s option in addition
> >> to -F option.  To support old behavior, it'll also prepend 'overhead'
> >> field to the sort keys unless you give -F option explicitly.
> >
> > So I am struggling a little bit to get this working correctly.  I had it
> > in my head that I could sort internally with -s and re-sort the output
> > based on -F, but it doesn't seem to be working that way.
> 
> Hmm.. probably it's me miss something on perf mem side..  I don't have
> an access to a machine to test it now.
> 
> >
> > For example with
> >
> > ./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

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/