Linux Perf Users
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Clark Williams <williams@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCHES v2 0/7] Initial support for some Rust tags + way to ask for CU merging at load time
Date: Thu, 18 Jun 2026 14:31:56 -0300	[thread overview]
Message-ID: <ajQrjKyBjjR1vxp6@x1> (raw)
In-Reply-To: <20260618151606.82747-1-acme@kernel.org>

On Thu, Jun 18, 2026 at 12:15:59PM -0300, Arnaldo Carvalho de Melo wrote:
> Hi,
> 
>         Here is a series with some initial support for some Rust DWARF
> tags and a way to ask for CUs to be merged just like we do for LTO to
> cope with inter CU tag references.

Sorry Namhyung, used the wrong send mail script :-\ This one should have
been sent to the pahole mailing list, doing that now.

- Arnaldo
 
>         This makes one of the regression tests to pass again as perf now
> has some rust source files and thus Rust CUs in a perf binary built with
> DWARF, which is used to test pahole's pretty printing features, where it
> uses the DWARF in a perf binary to decode perf.data records.
> 
> 	Now this is implemented as --features=force_cu_merging,
> following a suggestion from Alan, so that we can ask for this, that
> albeit not optimal is a way to handle Rust and other cases that may need
> this CU merging approach while we don't have something that works in
> parallel as without this option.
> 
> - Arnaldo
> 
> Arnaldo Carvalho de Melo (7):
>   dwarf_loader: Initial support for DW_TAG_variant_part
>   dwarf_loader: Allow forcing the merge of CUs for solving inter CU tag
>     references
>   dwarf_loader: Initial support for DW_TAG_subprogram in
>     DW_TAG_enumeration
>   encoders: Fix diagnostic messages for unexpected tags in enumerations
>   dwarves_fprintf: Accumulate function__fprintf return value in
>     enumeration printing
>   dwarves: Use tag__delete for enumeration children
>   btf_encoder: Remove unused variables
> 
>  btf_encoder.c               | 17 ++++++----
>  ctf_encoder.c               | 16 ++++++---
>  dwarf_loader.c              | 67 +++++++++++++++++++++++++++++++------
>  dwarves.c                   | 35 +++++++++++++++----
>  dwarves.h                   | 19 ++++++++++-
>  dwarves_emit.c              | 10 +++---
>  dwarves_fprintf.c           | 44 +++++++++++++++++-------
>  man-pages/pahole.1          | 17 ++++++++--
>  pahole.c                    | 20 ++++++++---
>  tests/prettify_perf.data.sh |  4 +--
>  10 files changed, 195 insertions(+), 54 deletions(-)
> 
> -- 
> 2.54.0

      parent reply	other threads:[~2026-06-18 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 15:15 [PATCHES v2 0/7] Initial support for some Rust tags + way to ask for CU merging at load time Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 1/7] dwarf_loader: Initial support for DW_TAG_variant_part Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 2/7] dwarf_loader: Allow forcing the merge of CUs for solving inter CU tag references Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 3/7] dwarf_loader: Initial support for DW_TAG_subprogram in DW_TAG_enumeration Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 4/7] encoders: Fix diagnostic messages for unexpected tags in enumerations Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 5/7] dwarves_fprintf: Accumulate function__fprintf return value in enumeration printing Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 6/7] dwarves: Use tag__delete for enumeration children Arnaldo Carvalho de Melo
2026-06-18 15:16 ` [PATCH 7/7] btf_encoder: Remove unused variables Arnaldo Carvalho de Melo
2026-06-18 17:31 ` 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=ajQrjKyBjjR1vxp6@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=williams@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox