From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Chun-Tse Shao <ctshao@google.com>,
Suchit Karunakaran <suchitkarunakaran@gmail.com>
Subject: Re: [PATCH v2] perf lock contention: Allow 'mmap_lock' in -L/--lock-filter
Date: Thu, 4 Jun 2026 09:28:39 -0700 [thread overview]
Message-ID: <aiGnt_xUewsAYP2y@google.com> (raw)
In-Reply-To: <aiGGmN0jIsTHgUJH@x1>
On Thu, Jun 04, 2026 at 11:07:20AM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, May 05, 2026 at 04:11:35PM -0700, Namhyung Kim wrote:
> > The -L/--lock-filter option is to specify target locks by name or
> > address. It's basically for global locks where name or address is known
> > and fixed. But 'mmap_lock' is a per-process lock so it cannot be used
> > for the -L option.
> >
> > $ sudo perf lock con -ab -L mmap_lock
> > ignore unknown symbol: mmap_lock
> > libbpf: map 'addr_filter': failed to create: -EINVAL
> > libbpf: failed to load BPF skeleton 'lock_contention_bpf': -EINVAL
> > Failed to load lock-contention BPF skeleton
> > lock contention BPF setup failed
>
> Hi,
>
> Did this fell thru the cracks? :-)
Will check and send v3 soon.
Thanks,
Namhyung
prev parent reply other threads:[~2026-06-04 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 23:11 [PATCH v2] perf lock contention: Allow 'mmap_lock' in -L/--lock-filter Namhyung Kim
2026-05-05 23:32 ` sashiko-bot
2026-06-04 14:07 ` Arnaldo Carvalho de Melo
2026-06-04 16:28 ` Namhyung Kim [this message]
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=aiGnt_xUewsAYP2y@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ctshao@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=suchitkarunakaran@gmail.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.