From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Henry Castro <hcvcastro@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] perf: fix the probe finder location (.dwo files)
Date: Mon, 17 Oct 2022 09:37:53 -0300 [thread overview]
Message-ID: <Y01Mof9qMpFToRWY@kernel.org> (raw)
In-Reply-To: <20221005124710.30296-1-hcvcastro@gmail.com>
Em Wed, Oct 05, 2022 at 08:47:02AM -0400, Henry Castro escreveu:
> If the file object is compiled using -gsplit-dwarf,
> the probe finder location will fail.
>
> Signed-off-by: Henry Castro <hcvcastro@gmail.com>
> ---
>
> > Nit, I think we use _ELFUTILS_PREREQ(0, 171).
> Thank you
Masami, are you ok with this?
Namyung, how about you?
Thanks,
- Arnaldo
> > How about making it a separate function with 2 versions
> > depending on the elfutils? Then you can have the variables
> > only if they are used.
>
> > Something like get_source_from_debuginfod() in the same
> > file.
>
> Sounds good, but I prefer simplicity in the patch =),
> what do you think about
> {
> Dwarf_Die cudie, subdie;
> if (dwarf_cu_info() ..)
> ..
> }
>
> to resolve unused variable?
> }
>
>
> tools/perf/util/probe-finder.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/tools/perf/util/probe-finder.c b/tools/perf/util/probe-finder.c
> index 50d861a80f57..5f6781e712db 100644
> --- a/tools/perf/util/probe-finder.c
> +++ b/tools/perf/util/probe-finder.c
> @@ -1200,6 +1200,20 @@ static int debuginfo__find_probe_location(struct debuginfo *dbg,
> continue;
> }
>
> +#if _ELFUTILS_PREREQ(0, 171)
> + {
> + uint8_t unit_type;
> + Dwarf_Die cudie, subdie;
> +
> + /* Check separate debug information file. */
> + if (dwarf_cu_info(pf->cu_die.cu, NULL,
> + &unit_type, &cudie,
> + &subdie, NULL,
> + NULL, NULL) == 0
> + && unit_type == DW_UT_skeleton)
> + pf->cu_die = subdie;
> + }
> +#endif
> /* Check if target file is included. */
> if (pp->file)
> pf->fname = cu_find_realpath(&pf->cu_die, pp->file);
> --
> 2.20.1
--
- Arnaldo
next prev parent reply other threads:[~2022-10-17 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 18:10 [PATCH v2] perf: fix the probe finder location (.dwo files) Henry Castro
2022-10-04 18:54 ` Namhyung Kim
2022-10-05 12:47 ` [PATCH v3] " Henry Castro
2022-10-17 12:37 ` Arnaldo Carvalho de Melo [this message]
2023-01-29 23:21 ` Henry Castro
2023-02-02 1:21 ` Arnaldo Carvalho de Melo
2023-02-02 2:55 ` Namhyung Kim
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=Y01Mof9qMpFToRWY@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=hcvcastro@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).