From: Namhyung Kim <namhyung@kernel.org>
To: linux-kernel@vger.kernel.org, Chun-Tse Shao <ctshao@google.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, nick.forrington@arm.com,
linux-perf-users@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v8 0/4] Tracing contention lock owner call stack
Date: Fri, 28 Feb 2025 14:24:59 -0800 [thread overview]
Message-ID: <174078149997.322575.17228936303109215.b4-ty@kernel.org> (raw)
In-Reply-To: <20250227003359.732948-1-ctshao@google.com>
On Wed, 26 Feb 2025 16:28:52 -0800, Chun-Tse Shao wrote:
> For perf lock contention, the current owner tracking (-o option) only
> works with per-thread mode (-t option). Enabling call stack mode for
> owner can be useful for diagnosing why a system running slow in
> lock contention.
>
> Example output:
> $ sudo ~/linux/tools/perf/perf lock con -abvo -Y mutex -E16 perf bench sched pipe
> ...
> contended total wait max wait avg wait type caller
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-02-28 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 0:28 [PATCH v8 0/4] Tracing contention lock owner call stack Chun-Tse Shao
2025-02-27 0:28 ` [PATCH v8 1/4] perf lock: Add bpf maps for owner stack tracing Chun-Tse Shao
2025-02-27 0:28 ` [PATCH v8 2/4] perf lock: Retrieve owner callstack in bpf program Chun-Tse Shao
2025-02-27 0:28 ` [PATCH v8 3/4] perf lock: Make rb_tree helper functions generic Chun-Tse Shao
2025-02-27 0:28 ` [PATCH v8 4/4] perf lock: Report owner stack in usermode Chun-Tse Shao
2025-02-27 11:11 ` [PATCH v8 0/4] Tracing contention lock owner call stack Athira Rajeev
2025-02-27 19:20 ` Chun-Tse Shao
2025-02-28 22:24 ` 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=174078149997.322575.17228936303109215.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=ctshao@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=nick.forrington@arm.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