Re: [RFC PATCH 2/7] perf: add pipe-specific header read/write and event processing code

[Arnaldo Carvalho de Melo <acme@ghostprotocols.net>]

Em Sun, Mar 28, 2010 at 12:12:05AM +0100, Frederic Weisbecker escreveu:
> On Sat, Mar 27, 2010 at 08:05:05PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Mar 27, 2010 at 07:57:47PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Sat, Mar 27, 2010 at 04:14:57AM +0100, Frederic Weisbecker escreveu:
> > > > I actually wonder why you bother with a header in the pipe mode,
> > > > since it only contains MAGIC and its size.
> > > 
> > > Because he wants to detect endianness  :-)
> > 
> > Elaborating: piping over netcat from a big endian to a little endian
> > machine works because he used the ->needs_swap logic I implemented to
> > allow cross platform analysis.
> > 
> > Its just a matter of having the DSOS with matching build-ids in the
> > cache of the machine running 'perf report'.

> Ok, thanks for the explanations :-)

Humm, now that I read this again, the build-ids now are in the headers,
which will not be pushed as it is the last step in 'perf record', after
we stop recording events, so only if we make sure that the binaries are
the same is that we will be able to make sense of it over the network.

One more reason for the loader of DSOs to read the pre calculated
build-id ELF session to tell the kernel the 20 bytes build id that in
turn will inject it in the PERF_RECORD_MMAP event.

- Arnaldo