linux-kernel - Re: [PATCH 09/14] perf diff: Update perf diff documentation for multiple data comparison

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]

Message-ID: <20121129120612.GC1096@krava.brq.redhat.com>
Date:	Thu, 29 Nov 2012 13:06:12 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 09/14] perf diff: Update perf diff documentation for
 multiple data comparison

On Thu, Nov 29, 2012 at 08:52:18PM +0900, Namhyung Kim wrote:
> On Wed, 28 Nov 2012 14:52:44 +0100, Jiri Olsa wrote:
> > +COMPARISON
> > +----------
> > +The comparison is governed by the baseline file. The baseline perf.data
> > +file is iterated for samples. All other perf.data files specified on
> > +the command line are searched for the baseline sample pair. If the pair
> > +is found, specified computation is made and result is displayed.
> > +
> > +All samples from non-baseline perf.data files, that do not match any
> > +baseline entry, are displayed with empty space within baseline column
> > +and possible computation results (delta) in their related column.
> > +
> > +Example files samples:
> > +- file A with samples f1, f2, f3, f4,    f6
> > +- file B with samples     f2,     f4, f5
> > +- file C with samples f1, f2,         f5
> > +
> > +Example output:
> > +  x - computation takes place for pair
> > +  b - baseline sample percentage
> > +
> > +- perf diff A B C
> > +
> > +  baseline/A compute/B compute/C  samples
> > +  ---------------------------------------
> > +  b                    x          f1
> > +  b          x         x          f2
> > +  b                               f3
> > +  b          x                    f4
> > +  b                               f6
> > +             x         x          f5
> > +
> > +- perf diff B A C
> > +
> > +  baseline/B compute/A compute/C  samples
> > +  ---------------------------------------
> > +  b          x         x          f2
> > +  b          x                    f4
> > +  b                    x          f5
> > +             x         x          f1
> > +             x                    f3
> > +             x                    f6
> > +
> > +- perf diff C B A
> > +
> > +  baseline/C compute/B compute/A  samples
> > +  ---------------------------------------
> > +  b                    x          f1
> > +  b          x         x          f2
> > +  b          x                    f5
> > +                       x          f3
> > +             x         x          f4
> > +                       x          f6
> > +
> 
> It seems not work this way.  When I test multiple diff, I didn't get
> consecutive 'b's on the baseline column like your example in the cover
> letter of this series.

the baseline consecutiveness is just for sake of the doc readibility
it just presents logical output to get user some idea 

final output could be sorted by column data using -o <column number>

the initial diff output (no options) is sort of sorted by baseline ;)
you're right, that should be fixed.. by default sorted by baseline

jirka
--
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/