linux-kernel - Fwd: perf report/stat and symbolic event names

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

Date:	Wed, 2 Feb 2011 17:22:33 -0800
From:	Tipp Moseley <tipp@...gle.com>
To:	acme@...hat.com
Cc:	perfmon2-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	Stephane Eranian <eranian@...gle.com>
Subject: Fwd: perf report/stat and symbolic event names

Hey Arnaldo, Stephane suggested I mail you for this feature request to
the perf tool.
When I collect a "raw" event using perf record, perf report's output
is pretty useless.  E.g.:
# Events: 833  raw 0x3d500a0
So when I collect multiple events, I have to refer to the command line
used to collect the profile and line up the event flags to figure out
what I was collecting.  With multiple collection runs, this can become
quite confusing.
The perf.data file doesn't seem to have the symbolic name of the event present.
Do you think it would be reasonable to add a field to the profile to
include the symbolic description of the event as it was given on the
command line (e.g., "RS_UOPS_DISPATCHED:u:i:e:c=3")?
Tipp
--
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/