From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCHSET 0/7] perf lock: New lock contention tracepoints support (v4)
Date: Fri, 24 Jun 2022 15:59:55 -0300 [thread overview]
Message-ID: <YrYJq8UQ04FFN12/@kernel.org> (raw)
In-Reply-To: <CAM9d7cjD=at=AtKmvMLogjN6mieWVR2kk-HigxO01cvPPRGFBg@mail.gmail.com>
Em Fri, Jun 24, 2022 at 09:40:05AM -0700, Namhyung Kim escreveu:
>> Ping! Any comments?
I'll take a look and test it soon.
- Arnaldo
>
> On Wed, Jun 15, 2022 at 9:32 AM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > Hello,
> >
> > Kernel v5.19 will have a new set of tracepoints to track lock
> > contentions for various lock types. Unlike tracepoints in LOCKDEP and
> > LOCK_STAT, it's hit only for contended locks and lock names are not
> > available. So it needs to collect stack traces and display the caller
> > function instead.
> >
> > Changes in v4)
> > * add Acked-by from Ian
> > * more comments on trace_lock_handler
> > * don't create stats in the contention_end handler
> >
> > Changes in v3)
> > * fix build error
> > * support data from different kernels/machines
> > * skip bad stat unless there's actual bad ones
> >
> > Changes in v2)
> > * add Acked-by from Ian
> > * print time with a unit for compact output
> > * add some comments (Ian)
> > * remove already applied patch
> >
> > This patchset merely adds support for the new tracepoints to the
> > existing perf lock commands. So there's no change to the user. Later
> > I'll add new a sub-command dedicated to the tracepoints to make use of
> > the additional information.
> >
> > Example output:
> >
> > $ sudo perf lock record -a sleep 3
> >
> > $ perf lock report -F acquired,contended,avg_wait,wait_total
> >
> > Name acquired contended avg wait total wait
> >
> > update_blocked_a... 40 40 3.61 us 144.45 us
> > kernfs_fop_open+... 5 5 3.64 us 18.18 us
> > _nohz_idle_balance 3 3 2.65 us 7.95 us
> > tick_do_update_j... 1 1 6.04 us 6.04 us
> > ep_scan_ready_list 1 1 3.93 us 3.93 us
> > ...
> >
> > You can find the code in the 'perf/lock-contention-v4' branch at
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
> >
> > Thanks,
> > Namhyung
> >
> >
> > Namhyung Kim (7):
> > perf lock: Print wait times with unit
> > perf lock: Allow to use different kernel symbols
> > perf lock: Skip print_bad_events() if nothing bad
> > perf lock: Add lock contention tracepoints record support
> > perf lock: Handle lock contention tracepoints
> > perf record: Allow to specify max stack depth of fp callchain
> > perf lock: Look up callchain for the contended locks
> >
> > tools/perf/Documentation/perf-lock.txt | 7 +
> > tools/perf/Documentation/perf-record.txt | 5 +
> > tools/perf/builtin-lock.c | 426 ++++++++++++++++++++++-
> > tools/perf/util/callchain.c | 18 +-
> > 4 files changed, 434 insertions(+), 22 deletions(-)
> >
> >
> > base-commit: 9886142c7a2226439c1e3f7d9b69f9c7094c3ef6
> > --
> > 2.36.1.476.g0c4daa206d-goog
> >
--
- Arnaldo
next prev parent reply other threads:[~2022-06-24 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 16:32 [PATCHSET 0/7] perf lock: New lock contention tracepoints support (v4) Namhyung Kim
2022-06-15 16:32 ` [PATCH 1/7] perf lock: Print wait times with unit Namhyung Kim
2022-06-15 16:32 ` [PATCH 2/7] perf lock: Allow to use different kernel symbols Namhyung Kim
2022-06-15 16:32 ` [PATCH 3/7] perf lock: Skip print_bad_events() if nothing bad Namhyung Kim
2022-06-15 16:32 ` [PATCH 4/7] perf lock: Add lock contention tracepoints record support Namhyung Kim
2022-06-15 16:32 ` [PATCH 5/7] perf lock: Handle lock contention tracepoints Namhyung Kim
2022-06-15 16:32 ` [PATCH 6/7] perf record: Allow to specify max stack depth of fp callchain Namhyung Kim
2022-06-15 16:32 ` [PATCH 7/7] perf lock: Look up callchain for the contended locks Namhyung Kim
2022-06-24 16:40 ` [PATCHSET 0/7] perf lock: New lock contention tracepoints support (v4) Namhyung Kim
2022-06-24 18:59 ` Arnaldo Carvalho de Melo [this message]
2022-06-24 21:38 ` Namhyung Kim
2022-07-07 17:03 ` Namhyung Kim
2022-07-12 12:57 ` Arnaldo Carvalho de Melo
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=YrYJq8UQ04FFN12/@kernel.org \
--to=acme@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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 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.