linux-kernel - Re: [PATCH 11/11] perf, tools, stat: Add extra output of counter values with -v

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] [day] [month] [year] [list]

Message-ID: <20160406151401.GE5945@kernel.org>
Date:	Wed, 6 Apr 2016 12:14:01 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	peterz@...radead.org, jolsa@...nel.org,
	linux-kernel@...r.kernel.org, mingo@...nel.org,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 11/11] perf, tools, stat: Add extra output of counter
 values with -v

Em Wed, Apr 06, 2016 at 08:10:08AM -0700, Andi Kleen escreveu:
> On Wed, Apr 06, 2016 at 11:32:20AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Apr 04, 2016 at 01:41:54PM -0700, Andi Kleen escreveu:
> > > From: Andi Kleen <ak@...ux.intel.com>
> > > 
> > > Add debug output of raw counter values per CPU when
> > > perf stat -v is specified, together with their cpu numbers.
> > > This is very useful to debug problems with per core counters,
> > > where we can normally only see aggregated values.
> > 
> > Can we do it only when per CPU is in place?
> 
> Even then it is useful because the output is aggregated,
> so we don't know which CPU reported what.
> 
> Can perhaps increase the verbose threshold and only
> print it for -vv or -vvv ?

Yeah, that would be better, this way people will not get two identical
lines for a common usecase when using -v.

- Arnaldo