linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Brennan <stephen.s.brennan@oracle.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	linux-perf-users@vger.kernel.org,
	James Clark <james.clark@linaro.org>,
	Ian Rogers <irogers@google.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Chaitanya S Prakash <chaitanyas.prakash@arm.com>,
	linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 0/3] Support .gnu_debugdata for symbols in perf
Date: Mon, 10 Mar 2025 12:52:40 -0300	[thread overview]
Message-ID: <Z88KyA4PCzhMa-fK@x1> (raw)
In-Reply-To: <20250307232206.2102440-1-stephen.s.brennan@oracle.com>

On Fri, Mar 07, 2025 at 03:22:00PM -0800, Stephen Brennan wrote:
> Hello all,
>
> This series adds the ability to read symbols from the ".gnu_debugdata" section
> of DSOs. More details are the cover letter of v1. This only has one small change
> from v2: it adds the missing entry in dso__symtab_origin(). Its lack resulted in
> truncating the output of symbols in "perf report -v" -- thanks to Arnaldo for
> testing and catching that.
>
> v2: https://lore.kernel.org/linux-perf-users/20250220185512.3357820-1-stephen.s.brennan@oracle.com/
> v1: https://lore.kernel.org/linux-perf-users/20250213190542.3249050-1-stephen.s.brennan@oracle.com/
>
> Stephen Brennan (3):
>   tools: perf: add dummy functions for !HAVE_LZMA_SUPPORT
>   tools: perf: add LZMA decompression from FILE
>   tools: perf: support .gnu_debugdata for symbols

Next time please follow the convention on subject lines in tools/perf:

36e7748d33bf6a82 (perf-tools-next/perf-tools-next) perf tests: Fix data symbol test with LTO builds
e1f5bb18a7b25cac perf report: Fix memory leaks in the hierarchy mode
e242df05ee5f2ab0 perf report: Use map_symbol__copy() when copying callchains
4c3f09e35ca999f6 perf annotate: Return errors from disasm_line__parse_powerpc()
dab8c32ece27c7d8 perf annotate: Add annotation_options.disassembler_used
b0920abe0d529101 perf report: Do not process non-JIT BPF ksymbol events
2c744f38da7aeae7 perf test: Fix leak in "Synthesize attr update" test
41453107bfc30083 perf machine: Fix insertion of PERF_RECORD_KSYMBOL related kernel maps
e0e4e0b8b7fabd8c perf maps: Add missing map__set_kmap_maps() when replacing a kernel map
0d11fab32714a2da perf maps: Fixup maps_by_name when modifying maps_by_address
f7a46e028c394cd4 perf machine: Fixup kernel maps ends after adding extra maps
25d9c0301d36f4d8 perf maps: Set the kmaps for newly created/added kernel maps
99deaf5578cd768f perf maps: Introduce map__set_kmap_maps() for kernel maps
74fb903b212925ca perf script: Fix output type for dynamically allocated core PMU's
957d194163bf983d perf bench: Fix perf bench syscall loop count
b627b443ccfbdd2c perf test: Simplify data symbol test
f04c7ef35256beea perf test: Add timeout to datasym workload
15bcfb96d0ddbc1b perf test: Add trace record and replay test
38672c5033c3aebc perf test: Skip perf trace tests when running as non-root
3fb29a7514e727ca perf test: Skip perf probe tests when running as non-root
⬢ [acme@toolbox perf-tools-next]$

I.e. perf, followed by the tool or class (machine, maps, etc), followed
by : and then the summary, starting with a capital letter.

I retested and everything looks great, so please add my:

Reviewed-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>

Thanks,

- Arnaldo

>  tools/perf/util/compress.h   |  20 +++++++
>  tools/perf/util/dso.c        |   3 +
>  tools/perf/util/dso.h        |   1 +
>  tools/perf/util/lzma.c       |  29 ++++++----
>  tools/perf/util/symbol-elf.c | 106 ++++++++++++++++++++++++++++++++++-
>  tools/perf/util/symbol.c     |   2 +
>  6 files changed, 148 insertions(+), 13 deletions(-)
> 
> -- 
> 2.43.5

  parent reply	other threads:[~2025-03-10 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 23:22 [PATCH v3 0/3] Support .gnu_debugdata for symbols in perf Stephen Brennan
2025-03-07 23:22 ` [PATCH v3 1/3] tools: perf: add dummy functions for !HAVE_LZMA_SUPPORT Stephen Brennan
2025-03-07 23:22 ` [PATCH v3 2/3] tools: perf: add LZMA decompression from FILE Stephen Brennan
2025-03-07 23:22 ` [PATCH v3 3/3] tools: perf: support .gnu_debugdata for symbols Stephen Brennan
2025-03-10 15:52 ` Arnaldo Carvalho de Melo [this message]
2025-03-10 21:32   ` [PATCH v3 0/3] Support .gnu_debugdata for symbols in perf Namhyung Kim
2025-03-10 23:42     ` Stephen Brennan
2025-03-11 16:11 ` Namhyung Kim

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=Z88KyA4PCzhMa-fK@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=chaitanyas.prakash@arm.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stephen.s.brennan@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).