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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100323193246.GA32432@elte.hu>
Date:	Tue, 23 Mar 2010 20:32:46 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arnaldo Carvalho de Melo <acme@...radead.org>
Cc:	linux-kernel@...r.kernel.org,
	Fr?d?ric Weisbecker <fweisbec@...il.com>,
	Mike Galbraith <efault@....de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [PATCH 1/1] perf archive: Explain how to use the generated
 tarball


* Arnaldo Carvalho de Melo <acme@...radead.org> wrote:

> Em Tue, Mar 23, 2010 at 07:49:29PM +0100, Ingo Molnar escreveu:
> > * Arnaldo Carvalho de Melo <acme@...radead.org> wrote:
> > 
> > > From: Arnaldo Carvalho de Melo <acme@...hat.com>
> > > 
> > > [root@...pio ~]# perf archive
> > > Now please run:
> > > 
> > > $ tar xvf perf.data.tar.bz2 -C ~/.debug
> > > 
> > > wherever you need to run 'perf report' on.
> > > [root@...pio ~]#
> > 
> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/