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: <BANLkTi=UKJ2Ztkcui_+8UHF16b_8mTvpnA@mail.gmail.com>
Date:	Fri, 13 May 2011 22:32:58 +0200
From:	Wim Heirman <wim@...rman.net>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	David Ahern <dsahern@...il.com>, 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

Hi,

> 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.

Thanks, this is exactly what I'm looking for. In 2.6.32 (Ubuntu 10.04)
it works, although if I use --pid rather than the -- <command> variant
the first thread seams to be missing. In 2.6.38 (Ubuntu 11.04) the
first thread is missing in both use cases, and I get one column per
processor (which in itself is fine).

Regards,
Wim
--
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/