Cross platform perf.data analysis support

There are still some problems related to loading vmlinux files, but those are unrelated to the feature implemented in this patch, so will get fixed in the next patches, but here are some results: 1. collect perf.data file on a Fedora 12 machine, x86_64, 64-bit userland 2. transfer it to a Debian Testing machine, PARISC64, [...]

perf on parisc64

It built, after removing -fstack-protector-all that is not available for that target and suppressing the libelf-dev tests. Transferred a perf.data file created in a i386 machine and… it fails. Endianness issues, I guess. Will fully investigate this in the next days.

Modules encoded

Ended up encoding modules as PERF_RECORD_MMAP events details at: http://lkml.org/lkml/2010/1/7/370. Lets see how people react.

Recording where modules were loaded in perf.data

While trying to fix the build-id generation so as not to produce duplicates, I noticed another problem that needs to be solved before we can introduce perf archive and be able to analyse a perf.data file recorded in one machine on another, possibly with a different architecture and OS. The problem is similar to the [...]