From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Remi Bernon <rbernon@codeweavers.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@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 v3 1/3] perf dso: Use libbfd to read build_id and .gnu_debuglink section
Date: Thu, 3 Sep 2020 13:51:32 -0300 [thread overview]
Message-ID: <20200903165132.GA3495158@kernel.org> (raw)
In-Reply-To: <20200903002519.GA3487700@kernel.org>
Em Wed, Sep 02, 2020 at 09:25:19PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Aug 21, 2020 at 06:52:36PM +0200, Remi Bernon escreveu:
> > Wine generates PE binaries for most of its modules and perf is unable
> > to parse these files to get build_id or .gnu_debuglink section.
> >
> > Using libbfd when available, instead of libelf, makes it possible to
> > resolve debug file location regardless of the dso binary format.
> >
> > Signed-off-by: Remi Bernon <rbernon@codeweavers.com>
> > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Jiri Olsa <jolsa@redhat.com>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Jacek Caban <jacek@codeweavers.com>
> > ---
> >
> > v3: Rebase and small changes to PATCH 2/3 and and PATCH 3/3.
> >
> > tools/perf/util/symbol-elf.c | 80 ++++++++++++++++++++++++++++++++++--
> > 1 file changed, 77 insertions(+), 3 deletions(-)
> >
> > diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
> > index 8cc4b0059fb0..f7432c4a4154 100644
> > --- a/tools/perf/util/symbol-elf.c
> > +++ b/tools/perf/util/symbol-elf.c
> > @@ -50,6 +50,10 @@ typedef Elf64_Nhdr GElf_Nhdr;
> > #define DMGL_ANSI (1 << 1) /* Include const, volatile, etc */
> > #endif
> >
> > +#ifdef HAVE_LIBBFD_SUPPORT
>
> So, the feature test should also test for the buildid struct field, see
> below:
>
> > +#define PACKAGE 'perf'
> > +#include <bfd.h>
> > +#else
> > #ifdef HAVE_CPLUS_DEMANGLE_SUPPORT
> > extern char *cplus_demangle(const char *, int);
> >
> > @@ -65,9 +69,7 @@ static inline char *bfd_demangle(void __maybe_unused *v,
> > {
> > return NULL;
> > }
> > -#else
> > -#define PACKAGE 'perf'
> > -#include <bfd.h>
> > +#endif
> > #endif
> > #endif
> >
> > @@ -530,6 +532,36 @@ static int elf_read_build_id(Elf *elf, void *bf, size_t size)
> > return err;
> > }
> >
> > +#ifdef HAVE_LIBBFD_SUPPORT
> > +
> > +int filename__read_build_id(const char *filename, void *bf, size_t size)
> > +{
> > + int err = -1;
> > + bfd *abfd;
> > +
> > + abfd = bfd_openr(filename, NULL);
> > + if (!abfd)
> > + return -1;
> > +
> > + if (!bfd_check_format(abfd, bfd_object)) {
> > + pr_debug2("%s: cannot read %s bfd file.\n", __func__, filename);
> > + goto out_close;
> > + }
> > +
> > + if (!abfd->build_id || abfd->build_id->size > size)
> > + goto out_close;
>
> amazonlinux:1, centos:6, debian:8, mageia:5, oraclelinux:6, ubuntu:14.04
> fail, its all old stuff, but adding a reference to abfd->build_id to the
> feature test that ends up defining HAVE_LIBBFD_SUPPORT will solve that,
> I'll do it tomorrow morning if you don't beat me to it.
>
> util/symbol-elf.c: In function 'filename__read_build_id':
> util/symbol-elf.c:551:11: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> if (!abfd->build_id || abfd->build_id->size > size)
> ^~
> util/symbol-elf.c:551:29: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> if (!abfd->build_id || abfd->build_id->size > size)
> ^~
> util/symbol-elf.c:554:17: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> memcpy(bf, abfd->build_id->data, abfd->build_id->size);
> ^~
> util/symbol-elf.c:554:39: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> memcpy(bf, abfd->build_id->data, abfd->build_id->size);
> ^~
> util/symbol-elf.c:555:18: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> memset(bf + abfd->build_id->size, 0, size - abfd->build_id->size);
> ^~
> util/symbol-elf.c:555:50: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> memset(bf + abfd->build_id->size, 0, size - abfd->build_id->size);
> ^~
> util/symbol-elf.c:556:12: error: 'bfd {aka struct bfd}' has no member named 'build_id'
> err = abfd->build_id->size;
> ^~
> CC /tmp/build/perf/util/cap.o
> make[4]: *** [/tmp/build/perf/util/symbol-elf.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> LD /tmp/build/perf/util/scripting-engines/perf-in.o
> LD /tmp/build/perf/util/intel-pt-decoder/perf-in.o
> make[3]: *** [util] Error 2
> make[2]: *** [/tmp/build/perf/perf-in.o] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
> make: Leaving directory `/git/linux/tools/perf'
> + exit 1
> [perfbuilder@five ~]$
So, I have the cset at the end of this message in front of your series +
the following patch applied to your patch, the debuglink part seems ok
and can continue depending on just libbfd, having or not abfd->buildid.
- Arnaldo
diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
index f7432c4a4154a149..94a156df22d5a8d3 100644
--- a/tools/perf/util/symbol-elf.c
+++ b/tools/perf/util/symbol-elf.c
@@ -532,7 +532,7 @@ static int elf_read_build_id(Elf *elf, void *bf, size_t size)
return err;
}
-#ifdef HAVE_LIBBFD_SUPPORT
+#ifdef HAVE_LIBBFD_BUILDID_SUPPORT
int filename__read_build_id(const char *filename, void *bf, size_t size)
{
@@ -560,7 +560,7 @@ int filename__read_build_id(const char *filename, void *bf, size_t size)
return err;
}
-#else
+#else // HAVE_LIBBFD_BUILDID_SUPPORT
int filename__read_build_id(const char *filename, void *bf, size_t size)
{
@@ -589,7 +589,7 @@ int filename__read_build_id(const char *filename, void *bf, size_t size)
return err;
}
-#endif
+#endif // HAVE_LIBBFD_BUILDID_SUPPORT
int sysfs__read_build_id(const char *filename, void *build_id, size_t size)
{
next prev parent reply other threads:[~2020-09-03 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 16:52 [PATCH v3 1/3] perf dso: Use libbfd to read build_id and .gnu_debuglink section Remi Bernon
2020-08-21 16:52 ` [PATCH v3 2/3] perf symbols: Try reading the symbol table with libbfd Remi Bernon
2020-08-21 16:52 ` [PATCH v3 3/3] perf tests: Add test for PE binary format support Remi Bernon
2020-08-26 11:47 ` [PATCH v3 1/3] perf dso: Use libbfd to read build_id and .gnu_debuglink section Jiri Olsa
2020-09-03 0:25 ` Arnaldo Carvalho de Melo
2020-09-03 16:51 ` Arnaldo Carvalho de Melo [this message]
2020-09-04 7:57 ` Remi Bernon
2020-09-04 19:03 ` Arnaldo Carvalho de Melo
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=20200903165132.GA3495158@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jacek@codeweavers.com \
--cc=jolsa@redhat.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 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.