perf report does not get along with perf record -A
A message that is not in the archive (sent off-list or not yet received): [email protected]
I'm working under the assumption that if I want to collect statistics from multiple runs of a program, I can do this by running perf record prog; perf record -A prog; perf record -A prog
I've found that running perf record twice results in perf report hanging, and running it more than twice results in perf report first spewing a message about invalid formats, then crashing. A log of the session, as well as the binary, its input and perf.data can be found at:
http://www.club.cc.cmu.edu/~mjrosenb/ion/perf_crash.tar.gz
Thanks --Marty
Quoted 5 lines · Martin Rosenberg
I'm working under the assumption that if I want to collect statistics from multiple runs of a program, I can do this by running perf record prog; perf record -A prog; perf record -A prog
I've found that running perf record twice results in perf report hanging, and running it more than twice results in perf report first spewing a message about invalid formats, then crashing. A log of the session, as well as the binary, its input and perf.data can be found at:
What does 'perf --version' show?
David
Derp. I went through all of that effort to make sure I had recorded everything about my setup, and I forgot the versiou
perf version 3.2.17
built unpatched from a 3.4.4 tarball
----- Original Message -----
From: "David Ahern" <[email protected]>
To: "Martin Rosenberg" <[email protected]>
Cc: [email protected]
Sent: Monday, June 25, 2012 9:40:49 PM
Subject: Re: perf report does not get along with perf record -A
Quoted 5 lines · Martin Rosenberg
I'm working under the assumption that if I want to collect statistics from multiple runs of a program, I can do this by running perf record prog; perf record -A prog; perf record -A prog
I've found that running perf record twice results in perf report hanging, and running it more than twice results in perf report first spewing a message about invalid formats, then crashing. A log of the session, as well as the binary, its input and perf.data can be found at:
What does 'perf --version' show?
David
Quoted 7 lines · Martin Rosenberg
I'm working under the assumption that if I want to collect statistics from multiple runs of a program, I can do this by running perf record prog; perf record -A prog; perf record -A prog
I've found that running perf record twice results in perf report hanging, and running it more than twice results in perf report first spewing a message about invalid formats, then crashing. A log of the session, as well as the binary, its input and perf.data can be found at:
Append has been broken for a long time (v2.6.36 last working version).
git bisect points to:
commit 55b44629f599a2305265ae9c77f9d9bcfd6ddc17
Author: Thomas Gleixner <[email protected]> Date: Tue Nov 30 17:49:46 2010 +0000
perf session: Use sensible mmap size
On 64bit we can map the whole file in one go, on 32bit we can at
least map
32MB and not map/unmap tiny chunks of the file.
Base the progress bar on 1/16 of the data size.
Preparatory patch to get rid of the malloc/memcpy/free of trace data.
Cc: Ingo Molnar <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Frederic Weisbecker <[email protected]>
LKML-Reference: <[email protected]>
:040000 040000 a0d7ddfb30b562a548052b12b142b579aa888886 dd4e368cbdf0ba24126afcc0fe42feea3b68f4a7 M tools
The commit right before that one (d65132) dumps some errors, but at least does not hang -- spinning in the event processing.
David