All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Fr?d?ric Weisbecker <fweisbec@gmail.com>,
	Mike Galbraith <efault@gmx.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/1] perf archive: Explain how to use the generated tarball
Date: Tue, 23 Mar 2010 20:32:46 +0100	[thread overview]
Message-ID: <20100323193246.GA32432@elte.hu> (raw)
In-Reply-To: <20100323192952.GA23584@ghostprotocols.net>


* 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.

> 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.

	Ingo

  reply	other threads:[~2010-03-23 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 17:33 [PATCH 1/1] perf archive: Explain how to use the generated tarball Arnaldo Carvalho de Melo
2010-03-23 18:49 ` Ingo Molnar
2010-03-23 19:29   ` Arnaldo Carvalho de Melo
2010-03-23 19:32     ` Ingo Molnar [this message]
2010-03-23 19:53       ` Arnaldo Carvalho de Melo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100323193246.GA32432@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.