From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: acme@kernel.org, adrian.hunter@intel.com, bvanassche@acm.org,
elver@google.com, james.clark@linaro.org, jolsa@kernel.org,
justinstitt@google.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, llvm@lists.linux.dev,
mingo@redhat.com, morbo@google.com, nathan@kernel.org,
ndesaulniers@google.com, peterz@infradead.org
Subject: Re: [PATCH v12 12/20] perf dsos: Use read lock fast path in dsos__findnew_id()
Date: Wed, 11 Nov 2026 22:53:36 -0800 [thread overview]
Message-ID: <avVicOfEPnzFYChm@google.com> (raw)
In-Reply-To: <20261111174213.3526604-13-irogers@google.com>
On Wed, Nov 11, 2026 at 09:42:04AM -0800, Ian Rogers wrote:
> In dsos__findnew_id(), try finding the DSO under the read lock first and
> only acquire the write lock when a new DSO must be inserted or an
> existing DSO needs its ID updated (checked via dso__needs_improve_id()).
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/dso.c | 16 +++++++++++++++-
> tools/perf/util/dso.h | 1 +
> tools/perf/util/dsos.c | 10 ++++++++++
> 3 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/dso.c b/tools/perf/util/dso.c
> index f0e02062c09c..4dc518f7cb7d 100644
> --- a/tools/perf/util/dso.c
> +++ b/tools/perf/util/dso.c
> @@ -1685,6 +1685,18 @@ const struct dso_id dso_id_empty = {
> }
> };
>
> +bool dso__needs_improve_id(const struct dso *dso, const struct dso_id *id)
> +{
> + const struct dso_id *dso_id = dso__id_const(dso);
> +
> + if (!id)
> + return false;
> +
> + return (id->mmap2_valid && !dso_id->mmap2_valid) ||
> + (id->mmap2_ino_generation_valid && !dso_id->mmap2_ino_generation_valid) ||
> + (build_id__is_defined(&id->build_id) && !build_id__is_defined(&dso_id->build_id));
Don't we prefer build-ID over inode? I'm curious if it needs to check
existing build-ID is defined first and return true. Any chance it'd
overwrite a build-ID with an inode?
Thanks,
Namhyung
> +}
> +
> void __dso__improve_id(struct dso *dso, const struct dso_id *id)
> {
> struct dsos *dsos = dso__dsos(dso);
> @@ -1692,6 +1704,8 @@ void __dso__improve_id(struct dso *dso, const struct dso_id *id)
> bool changed = false;
>
> /* dsos write lock held by caller. */
> + if (!id)
> + return;
>
> if (id->mmap2_valid && !dso_id->mmap2_valid) {
> dso_id->maj = id->maj;
> @@ -1715,7 +1729,7 @@ void __dso__improve_id(struct dso *dso, const struct dso_id *id)
>
> int dso_id__cmp(const struct dso_id *a, const struct dso_id *b)
> {
> - if (a == &dso_id_empty || b == &dso_id_empty) {
> + if (!a || !b || a == &dso_id_empty || b == &dso_id_empty) {
> /* There is no valid data to compare so the comparison always returns identical. */
> return 0;
> }
> diff --git a/tools/perf/util/dso.h b/tools/perf/util/dso.h
> index 9e38b3b69e9b..df1748763d95 100644
> --- a/tools/perf/util/dso.h
> +++ b/tools/perf/util/dso.h
> @@ -802,6 +802,7 @@ void dso__delete(struct dso *dso);
> int dso__cmp_id(struct dso *a, struct dso *b);
> void dso__set_short_name(struct dso *dso, const char *name, bool name_allocated);
> void dso__set_long_name(struct dso *dso, const char *name, bool name_allocated);
> +bool dso__needs_improve_id(const struct dso *dso, const struct dso_id *id);
> void __dso__improve_id(struct dso *dso, const struct dso_id *id);
>
> int dso__name_len(const struct dso *dso);
> diff --git a/tools/perf/util/dsos.c b/tools/perf/util/dsos.c
> index fbbf98c4ccae..1b3f8b84ed30 100644
> --- a/tools/perf/util/dsos.c
> +++ b/tools/perf/util/dsos.c
> @@ -349,6 +349,16 @@ static struct dso *__dsos__findnew_id(struct dsos *dsos, const char *name, const
> struct dso *dsos__findnew_id(struct dsos *dsos, const char *name, const struct dso_id *id)
> {
> struct dso *dso;
> +
> + down_read(&dsos->lock);
> + dso = __dsos__find_id(dsos, name, id, false, /*write_locked=*/false);
> + if (dso && !dso__needs_improve_id(dso, id)) {
> + up_read(&dsos->lock);
> + return dso;
> + }
> + up_read(&dsos->lock);
> + dso__put(dso);
> +
> down_write(&dsos->lock);
> dso = __dsos__findnew_id(dsos, name, id);
> up_write(&dsos->lock);
> --
> 2.56.0.542.g3ef89b7020-goog
>
next prev parent reply other threads:[~2026-11-12 6:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 17:41 [PATCH v12 00/20] tools/perf: Adopt kernel compiler-context-analysis.h annotations Ian Rogers
2026-11-11 17:41 ` [PATCH v12 01/20] compiler-context-analysis: Avoid unused parameter warning in _context_unsafe_alias() Ian Rogers
2026-11-11 17:41 ` [PATCH v12 02/20] tools headers compiler: Synchronize compiler_types.h with the kernel sources Ian Rogers
2026-11-12 6:31 ` Namhyung Kim
2026-11-11 17:41 ` [PATCH v12 03/20] tools headers: Synchronize linux/compiler-context-analysis.h " Ian Rogers
2026-11-11 17:41 ` [PATCH v12 04/20] perf mutex: Use kernel style compiler-context-analysis.h annotations Ian Rogers
2026-11-11 17:41 ` [PATCH v12 05/20] perf build: Enable additional Clang thread-safety flags Ian Rogers
2026-11-11 17:41 ` [PATCH v12 06/20] perf comm: Add __guarded_by annotations to struct comm_strs Ian Rogers
2026-11-11 17:41 ` [PATCH v12 07/20] perf vdso: Fix unlocked __dsos__add() and race in __machine__addnew_vdso() Ian Rogers
2026-11-11 17:42 ` [PATCH v12 08/20] perf dsos: Skip BPF and OOL DSOs in dsos__find_kernel_dso() Ian Rogers
2026-11-12 6:44 ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 09/20] perf dsos: Ensure DSOs in auxtrace, machine, and symbol are in dsos Ian Rogers
2026-11-11 17:42 ` [PATCH v12 10/20] perf dso: Pass dso_data to close_data_fd() and dso__list_del() Ian Rogers
2026-11-11 17:42 ` [PATCH v12 11/20] perf dso: Use DEFINE_MUTEX for dso__data_open_lock Ian Rogers
2026-11-11 17:42 ` [PATCH v12 12/20] perf dsos: Use read lock fast path in dsos__findnew_id() Ian Rogers
2026-11-12 6:53 ` Namhyung Kim [this message]
2026-11-11 17:42 ` [PATCH v12 13/20] perf dso: Expand context analysis annotations Ian Rogers
2026-11-11 17:42 ` [PATCH v12 14/20] perf thread: Expand context analysis annotations to threads and namespaces_lock Ian Rogers
2026-11-11 17:42 ` [PATCH v12 15/20] perf intel-tpebs: Fix race in tpebs_stop() and tpebs_cmd.out fd handling Ian Rogers
2026-11-12 7:19 ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 16/20] perf intel-tpebs: Use DEFINE_MUTEX for tpebs_mtx Ian Rogers
2026-11-12 7:08 ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 17/20] perf config, intel-tpebs, env: Add __guarded_by and __must_hold annotations Ian Rogers
2026-11-12 7:06 ` Namhyung Kim
2026-11-11 17:42 ` [PATCH v12 18/20] perf maps: Fix lock inversion in maps__load_first() Ian Rogers
2026-11-11 17:42 ` [PATCH v12 19/20] perf maps: Fix map index lookup fallback and removal Ian Rogers
2026-11-11 17:42 ` [PATCH v12 20/20] perf maps: Add context analysis annotations Ian Rogers
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=avVicOfEPnzFYChm@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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