* Fwd: perf report/stat and symbolic event names
[not found] <AANLkTikrV3fQ-qsOANG5X7zes1wxbO9mX1eev3xB_OzF@mail.gmail.com>
@ 2011-02-03 1:22 ` Tipp Moseley
2011-02-03 13:40 ` Arnaldo Carvalho de Melo
1 sibling, 0 replies; 2+ messages in thread
From: Tipp Moseley @ 2011-02-03 1:22 UTC (permalink / raw
To: acme; +Cc: perfmon2-devel, linux-kernel, Stephane Eranian
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: perf report/stat and symbolic event names
[not found] <AANLkTikrV3fQ-qsOANG5X7zes1wxbO9mX1eev3xB_OzF@mail.gmail.com>
2011-02-03 1:22 ` Fwd: perf report/stat and symbolic event names Tipp Moseley
@ 2011-02-03 13:40 ` Arnaldo Carvalho de Melo
1 sibling, 0 replies; 2+ messages in thread
From: Arnaldo Carvalho de Melo @ 2011-02-03 13:40 UTC (permalink / raw
To: Tipp Moseley; +Cc: perfmon2-devel, linux-kernel, Stephane Eranian
Em Wed, Feb 02, 2011 at 05:18:21PM -0800, Tipp Moseley escreveu:
> 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")?
Its definetely a good idea to record in the perf.data header section the
command line that was passed to perf record.
A new tool, 'perf ls' could then look for files with the perf.data magic
number and show the contents of this section.
Extra enhancements would include globbing, so that one could do:
$ perf ls *UOPS*
$ perf ls *httpd*
Etc.
Recording the perf record on the header was suggested by Ingo a long
time ago, I just didn't got to implement it :-\
If you can try to implement it, please see how build ids are encoded in
the perf.data header.
Otherwise I'll try to do it at some point.
- Arnaldo
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-02-03 13:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTikrV3fQ-qsOANG5X7zes1wxbO9mX1eev3xB_OzF@mail.gmail.com>
2011-02-03 1:22 ` Fwd: perf report/stat and symbolic event names Tipp Moseley
2011-02-03 13:40 ` Arnaldo Carvalho de Melo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).