linux-kernel - Re: perf-stat per thread results

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: <20110513154410.GA6373@elte.hu>
Date:	Fri, 13 May 2011 17:44:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Ahern <dsahern@...il.com>
Cc:	Wim Heirman <wim@...rman.net>, linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Brice Goglin <Brice.Goglin@...ia.fr>
Subject: Re: perf-stat per thread results


* David Ahern <dsahern@...il.com> wrote:

> On 05/13/11 09:14, Wim Heirman wrote:
> > Hi all,
> > 
> > I'm using perf-stat to look at hardware performance counters for a
> > parallel program. Is there a way to get counter values for each thread
> > individually, rather than aggregated for the whole process? I know I
> > can attach to a specific thread using --tid=, but due to the time
> > required to find the tid and attach/detach this isn't accurate for
> > short-running programs.
> 
> perf-stat requires changes to dump counters per thread; it currently
> sums all threads into a single value.
> 
> > Or, alternatively, can I use perf record --stat and get an exact count
> > for each performance counter?
> 
> perf-record does not read values from hardware counters.

It's supposed to do that if --stat is specified, and it used to work - see this 
commit:

  8d51327090ac: perf report: Fix and improve the displaying of per-thread event counters

and the output there:

     #  PID   TID  cache-misses  cache-references
       4658  4659        495581           3238779
       4658  4662        498246           3236823
       4658  4663        499531           3243162

which appears to be roughly what Wim is asking for, AFAICT.

But this seems to have regressed meanwhile.

Thanks,

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