From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 00/10] perf symbol: Properly set DSO binary/symtab types
Date: Mon, 12 Oct 2026 16:07:33 -0700 [thread overview]
Message-ID: <as1oNTq4Fqv_wgag@google.com> (raw)
In-Reply-To: <CAP-5=fXg3LYS0ftt1WjDXgEh6DLjZcYQiVNv=ym7CAA9PyiQ1A@mail.gmail.com>
On Mon, Oct 12, 2026 at 02:41:27PM -0700, Ian Rogers wrote:
> On Sun, Oct 11, 2026 at 10:26 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > Hello,
> >
> > Currently we have 3 types for a DSO.
> >
> > * binary type: determines where to read binary instruction or data of the
> > DSO. Basically used by annotate. Some (special) DSOs like kallsyms or
> > JIT may not have the data though.
> >
> > * symtab type: determines where to read symbol tables. Set when symbols
> > in the DSO are loaded.
> >
> > * debug info type: determines where to read debug info. Used by srcline,
> > DWARF unwinding, data type profiling and so on. Often debug info is
> > saved in a separate file.
> >
> > Some DSOs may have the same type for 3 and others can have all different.
> > Previously it generally assumed binary type would be same as symtab type
> > but now I think we should not and only set the binary type as it's used.
> >
> > Also it should make sure that symtab type is set properly after loading
> > symbols in the DSO.
> >
> > Probably this patchset won't make any practical difference in runtime
> > behaviors but I think it's good to track them accurately.
>
> Except for nits and resolving the remaining Sashiko feedback on patch 6.
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks for your review!
I'll sent v4 with the fixes soon.
Thanks,
Namhyung
prev parent reply other threads:[~2026-10-12 23:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 5:25 [PATCH v3 00/10] perf symbol: Properly set DSO binary/symtab types Namhyung Kim
2026-10-12 5:25 ` [PATCH v3 01/10] perf tools: Remove redundant dso data init Namhyung Kim
2026-10-12 5:30 ` sashiko-bot
2026-10-12 5:25 ` [PATCH v3 02/10] perf tools: Try linked debug files for DSO debug info Namhyung Kim
2026-10-12 5:35 ` sashiko-bot
2026-10-12 5:25 ` [PATCH v3 03/10] perf symbol: Update symtab type of vmlinux from build-id cache Namhyung Kim
2026-10-12 5:38 ` sashiko-bot
2026-10-12 5:25 ` [PATCH v3 04/10] perf symbol: Set binary/symtab type for split kallsyms Namhyung Kim
2026-10-12 5:33 ` sashiko-bot
2026-10-12 5:25 ` [PATCH v3 05/10] perf symbol: Get rid of machine_or_dso_e_machine() Namhyung Kim
2026-10-12 5:44 ` sashiko-bot
2026-10-12 5:25 ` [PATCH v3 06/10] perf tools: Factor out dso__find_binary_type() Namhyung Kim
2026-10-12 5:38 ` sashiko-bot
2026-10-12 19:50 ` Namhyung Kim
2026-10-12 21:37 ` Ian Rogers
2026-10-12 5:25 ` [PATCH v3 07/10] perf symbol: Set binary type for JIT map DSOs Namhyung Kim
2026-10-12 5:34 ` sashiko-bot
2026-10-12 5:25 ` [PATCH v3 08/10] perf symbol: Do not set binary type from symtab type Namhyung Kim
2026-10-12 5:38 ` sashiko-bot
2026-10-12 5:26 ` [PATCH v3 09/10] perf annotate: Simplify symbol__disassemble() with dso binary_type Namhyung Kim
2026-10-12 5:36 ` sashiko-bot
2026-10-12 5:26 ` [PATCH v3 10/10] perf test: Fix dso data tests Namhyung Kim
2026-10-12 5:37 ` sashiko-bot
2026-10-12 21:41 ` [PATCH v3 00/10] perf symbol: Properly set DSO binary/symtab types Ian Rogers
2026-10-12 23:07 ` Namhyung Kim [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=as1oNTq4Fqv_wgag@google.com \
--to=namhyung@kernel.org \
--cc=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=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox