From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Dave Rigby <d.rigby@me.com>
Cc: linux-perf-users@vger.kernel.org,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] perf unwind: Set userdata for all __report_module paths
Date: Thu, 18 Feb 2021 14:13:48 -0300 [thread overview]
Message-ID: <YC6gTCIV+EHNaerJ@kernel.org> (raw)
In-Reply-To: <D53872E9-71B0-4F1F-8640-672CE1ABE344@me.com>
Em Thu, Feb 18, 2021 at 04:58:44PM +0000, Dave Rigby escreveu:
> I missed adding a link to the bugzilla issue: https://bugzilla.kernel.org/show_bug.cgi?id=211801
>
> Note sure what the recommended way of tagging that in the patch is…
I'll add a:
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=211801
tag,
Thanks,
- Arnaldo
>
> DaveR
>
> > On 18 Feb 2021, at 16:56, d.rigby@me.com wrote:
> >
> > From: Dave Rigby <d.rigby@me.com>
> >
> > When locating the dwarf module for a given address, __find_debuginfo()
> > requires a 'struct dso' passed via the userdata argument.
> >
> > However, this field is only set in __report_module() if the module is
> > found in via dwfl_addrmodule(), not if it is found later via dwfl_report_elf().
> >
> > Set userdata irrespective of how the dwarf module was found, as long
> > as we found a module.
> >
> > Fixes: bf53fc6b5f41 ("perf unwind: Fix separate debug info files when using elfutils' libdw's unwinder")
> > Cc: linux-perf-users@vger.kernel.org
> > Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
> > Cc: Jiri Olsa <jolsa@redhat.com>
> > ---
> > tools/perf/util/unwind-libdw.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
> >
> > diff --git a/tools/perf/util/unwind-libdw.c b/tools/perf/util/unwind-libdw.c
> > index 0ada907..a74b517 100644
> > --- a/tools/perf/util/unwind-libdw.c
> > +++ b/tools/perf/util/unwind-libdw.c
> > @@ -60,10 +60,8 @@ static int __report_module(struct addr_location *al, u64 ip,
> > mod = dwfl_addrmodule(ui->dwfl, ip);
> > if (mod) {
> > Dwarf_Addr s;
> > - void **userdatap;
> >
> > - dwfl_module_info(mod, &userdatap, &s, NULL, NULL, NULL, NULL, NULL);
> > - *userdatap = dso;
> > + dwfl_module_info(mod, NULL, &s, NULL, NULL, NULL, NULL, NULL);
> > if (s != al->map->start - al->map->pgoff)
> > mod = 0;
> > }
> > @@ -79,6 +77,13 @@ static int __report_module(struct addr_location *al, u64 ip,
> > al->map->start - al->map->pgoff, false);
> > }
> >
> > + if (mod) {
> > + void **userdatap;
> > +
> > + dwfl_module_info(mod, &userdatap, NULL, NULL, NULL, NULL, NULL, NULL);
> > + *userdatap = dso;
> > + }
> > +
> > return mod && dwfl_addrmodule(ui->dwfl, ip) == mod ? 0 : -1;
> > }
> >
> > --
> > 1.8.3.1
>
--
- Arnaldo
next prev parent reply other threads:[~2021-02-18 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 16:56 [PATCH] perf unwind: Set userdata for all __report_module paths d.rigby
2021-02-18 16:58 ` Dave Rigby
2021-02-18 17:13 ` Arnaldo Carvalho de Melo [this message]
2021-02-18 17:19 ` Arnaldo Carvalho de Melo
2021-02-18 17:21 ` Dave Rigby
2021-02-18 17:22 ` Jan Kratochvil
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=YC6gTCIV+EHNaerJ@kernel.org \
--to=acme@kernel.org \
--cc=d.rigby@me.com \
--cc=jan.kratochvil@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).