Re: [PATCH 1/1] perf archive: Explain how to use the generated tarball

[Arnaldo Carvalho de Melo <acme@infradead.org>]

Em Tue, Mar 23, 2010 at 08:32:46PM +0100, Ingo Molnar escreveu:
> 
> * Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> 
> > Em Tue, Mar 23, 2010 at 07:49:29PM +0100, Ingo Molnar escreveu:
> > > * Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> > > 
> > > > From: Arnaldo Carvalho de Melo <acme@redhat.com>
> > > > 
> > > > [root@doppio ~]# perf archive
> > > > Now please run:
> > > > 
> > > > $ tar xvf perf.data.tar.bz2 -C ~/.debug
> > > > 
> > > > wherever you need to run 'perf report' on.
> > > > [root@doppio ~]#
> > > 
> > > hm, i think it would be nicer to have a way to both pack and unpack an archive 
> > > that is in the current directory. Something like:
> > > 
> > >   perf archive pack
> > >   perf archive unpack
> > > 
> > > or so?
> > 
> > Yes, its just that this was easy enough to improve the current situation, 
> > this is still a shell script that I wrote as a way to show how to do some 
> > porcelain out of 'perf buildid-list'.
> > 
> > But it probably will be better to have it as a full fledged tool, as I can 
> > imagine people asking for .tar.xz support, and I also want to be able to 
> > tell it to strip debugging information, putting there just the symtabs, etc.
> 
> Yeah - although we definitely want to keep it relatively simple - robust 
> archiving and cross-system transport is abot simplicity.

Yeah, 'perf archive' will be enough and use the defaults we deem best,
but I just wanted to allow people to have some configurability to avoid
huge DWARF laden binaries, for instance, when all a class of users may
want is to do simple symbol resolution, not full blown source
annotation, pick the compressor du jour, etc.
 
> > So if you can get this one in, the current situation would be improved and 
> > I'll eventually get to implement your suggestion.
> 
> Sure, just wanted to mention this.

Notes taken! :-)

- Arnaldo