[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174078149997.322575.17228936303109215.b4-ty@kernel.org>
Date: Fri, 28 Feb 2025 14:24:59 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: linux-kernel@...r.kernel.org, Chun-Tse Shao <ctshao@...gle.com>
Cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
mark.rutland@....com, alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
irogers@...gle.com, adrian.hunter@...el.com, kan.liang@...ux.intel.com,
nick.forrington@....com, linux-perf-users@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH v8 0/4] Tracing contention lock owner call stack
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
Powered by blists - more mailing lists