[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174248644099.3704425.17283492904024257461.b4-ty@kernel.org>
Date: Thu, 20 Mar 2025 09:00:41 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Stephen Brennan <stephen.s.brennan@...cle.com>
Cc: linux-perf-users@...r.kernel.org, James Clark <james.clark@...aro.org>,
Ian Rogers <irogers@...gle.com>, linux-kernel@...r.kernel.org,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Mark Rutland <mark.rutland@....com>,
Chaitanya S Prakash <chaitanyas.prakash@....com>,
"Liang, Kan" <kan.liang@...ux.intel.com>,
Athira Rajeev <atrajeev@...ux.vnet.ibm.com>,
Adrian Hunter <adrian.hunter@...el.com>
Subject: Re: [PATCH] perf dso: fix dso__is_kallsyms() check
On Tue, 18 Mar 2025 16:00:11 -0700, Stephen Brennan wrote:
> Kernel modules for which we cannot find a file on-disk will have a
> dso->long_name that looks like "[module_name]". Prior to the commit
> listed in the fixes, the dso->kernel field would be zero (for user
> space), so dso__is_kallsyms() would return false. After the commit,
> kernel module DSOs are correctly labeled, but the result is that
> dso__is_kallsyms() erroneously returns true for those modules without a
> filesystem path.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists