From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: vmolnaro@redhat.com
Cc: linux-perf-users@vger.kernel.org, acme@redhat.com,
mpetlan@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] perf archive: Add new option '--all'
Date: Wed, 20 Dec 2023 10:59:33 -0300 [thread overview]
Message-ID: <ZYLzRV2MY33fBtuS@kernel.org> (raw)
In-Reply-To: <ZXihN3th3qbo6L8Z@kernel.org>
Em Tue, Dec 12, 2023 at 03:06:47PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Dec 12, 2023 at 05:59:08PM +0100, vmolnaro@redhat.com escreveu:
> > From: Veronika Molnarova <vmolnaro@redhat.com>
> >
> > Perf archive has limited functionality and people from Red Hat Global
> > Support Services sent a request for a new feature that would pack
> > perf.data file together with an archive with debug symbols created by
> > the command 'perf archive' as customers were being confused and often
> > would forget to send perf.data file with the debug symbols.
> >
> > Perf archive now accepts an option '--all' that generates archive
> > 'perf.all-hostname-date-time.tar.bz2' that holds file 'perf.data' and
> > a sub-tar 'perf.symbols.tar.bz2' with debug symbols. The functionality of
> > the command 'perf archive' was not changed.
>
> Thanks for working on this, I'll do some testing and apply, probably
> tomorrow.
I applied it, tested by doing a 'perf record' on an hybrid Intel Machine
(14700k) and then using --unpack on an hybrid ARM64 machine (rk3399-pc),
all working as expected:
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/commit/?h=tmp.perf-tools-next&id=624dda101e03c3a3a155d51e37a7bb7607cb760b
Some suggestions for further improvements:
acme@roc-rk3399-pc:~$ perf archive --unpack
Found target file for unpacking: ./perf.all-number-20231219-104854.tar.bz2
perf.data
perf.symbols.tar.bz2
tar: /home/acme/.debug: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
acme@roc-rk3399-pc:~$
Check if the ~/.debug directory is present, if not, create it.
Also maybe use:
Informative output
--checkpoint[=N]
Display progress messages every Nth record (default 10).
--checkpoint-action=ACTION
Run ACTION on each checkpoint.
with 'tar' to show some progress in decompressing the tarball.
- Arnaldo
prev parent reply other threads:[~2023-12-20 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 16:59 [PATCH 1/2] perf archive: Add new option '--all' vmolnaro
2023-12-12 16:59 ` [PATCH 2/2] perf archive: Add new option '--unpack' vmolnaro
2023-12-12 18:06 ` [PATCH 1/2] perf archive: Add new option '--all' Arnaldo Carvalho de Melo
2023-12-20 13:59 ` Arnaldo Carvalho de Melo [this message]
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=ZYLzRV2MY33fBtuS@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=vmolnaro@redhat.com \
/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.