From: Jiri Olsa <jolsa@redhat.com>
To: Remi Bernon <rbernon@codeweavers.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jacek Caban <jacek@codeweavers.com>
Subject: Re: [PATCH 2/3] perf symbols: Try reading the symbol table with libbfd
Date: Wed, 24 Jun 2020 15:25:45 +0200 [thread overview]
Message-ID: <20200624132545.GD2719003@krava> (raw)
In-Reply-To: <20200624103041.825746-2-rbernon@codeweavers.com>
On Wed, Jun 24, 2020 at 12:30:40PM +0200, Remi Bernon wrote:
SNIP
> +
> + symbols__insert(&dso->symbols, symbol);
> + }
> +#ifdef bfd_get_section
> +#undef bfd_asymbol_section
> +#endif
> +
> + symbols__fixup_end(&dso->symbols);
> + symbols__fixup_duplicate(&dso->symbols);
> + dso->adjust_symbols = 1;
> +
> + err = 0;
> +out_free:
> + free(symbols);
> +out_close:
> + bfd_close(abfd);
> + return err;
> +}
> +#endif
> +
> static bool dso__is_compatible_symtab_type(struct dso *dso, bool kmod,
> enum dso_binary_type type)
> {
> @@ -1695,6 +1816,7 @@ int dso__load(struct dso *dso, struct map *map)
> bool next_slot = false;
> bool is_reg;
> bool nsexit;
> + int bfdrc = -1;
> int sirc = -1;
>
> enum dso_binary_type symtab_type = binary_type_symtab[i];
> @@ -1713,12 +1835,19 @@ int dso__load(struct dso *dso, struct map *map)
> nsinfo__mountns_exit(&nsc);
>
> is_reg = is_regular_file(name);
> +#ifdef HAVE_LIBBFD_SUPPORT
> if (is_reg)
> + bfdrc = dso__load_bfd_symbols(dso, name);
> +#endif
so the comment says that we try bfd when the libelf fails,
but the code seems to do the oposite.. starts with bfd
and skip libelf if it's ok
jirka
> + if (is_reg && bfdrc < 0)
> sirc = symsrc__init(ss, dso, name, symtab_type);
>
> if (nsexit)
> nsinfo__mountns_enter(dso->nsinfo, &nsc);
>
> + if (bfdrc == 0)
> + break;
> +
> if (!is_reg || sirc < 0)
> continue;
>
> diff --git a/tools/perf/util/symbol.h b/tools/perf/util/symbol.h
> index ff4f4c47e148..11fe71f46d14 100644
> --- a/tools/perf/util/symbol.h
> +++ b/tools/perf/util/symbol.h
> @@ -175,6 +175,10 @@ int symbol__config_symfs(const struct option *opt __maybe_unused,
>
> struct symsrc;
>
> +#ifdef HAVE_LIBBFD_SUPPORT
> +int dso__load_bfd_symbols(struct dso *dso, const char *debugfile);
> +#endif
> +
> int dso__load_sym(struct dso *dso, struct map *map, struct symsrc *syms_ss,
> struct symsrc *runtime_ss, int kmodule);
> int dso__synthesize_plt_symbols(struct dso *dso, struct symsrc *ss);
> --
> 2.27.0
>
next prev parent reply other threads:[~2020-06-24 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 10:30 [PATCH 1/3] perf dso: Use libbfd to read build_id and .gnu_debuglink section Remi Bernon
2020-06-24 10:30 ` [PATCH 2/3] perf symbols: Try reading the symbol table with libbfd Remi Bernon
2020-06-24 13:25 ` Jiri Olsa [this message]
2020-06-24 13:40 ` Rémi Bernon
[not found] ` <32a0da28-aca7-34b0-adb2-b0f61021fba8@codeweavers.com>
2020-07-08 18:33 ` Jiri Olsa
2020-06-24 10:30 ` [PATCH 3/3] perf tests: Add test for PE binary format support Remi Bernon
2020-06-24 13:10 ` Jiri Olsa
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=20200624132545.GD2719003@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jacek@codeweavers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rbernon@codeweavers.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