[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240513091413.738537-1-nick.forrington@arm.com>
Date: Mon, 13 May 2024 09:14:11 +0000
From: Nick Forrington <nick.forrington@....com>
To: linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Cc: Nick Forrington <nick.forrington@....com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>
Subject: [PATCH v4 0/1] Perf lock improvements
Improvement to command line handling for perf lock info.
---
v1: https://lore.kernel.org/all/20231031120526.11502-1-nick.forrington@arm.com/
v2:
* Drop previous "perf lock report: Restore aggregation by caller by
default" patch. Not required for newly collected data with LOCKDEP
tracepoints.
* Display map and thread info (rather than an error) when neither or
both of --map and --thread are specified.
v3:
* Update --help output
v4:
* Remove redundant error handling
Nick Forrington (1):
perf lock info: Display both map and thread by default
tools/perf/Documentation/perf-lock.txt | 4 ++--
tools/perf/builtin-lock.c | 27 ++++++++++++++------------
2 files changed, 17 insertions(+), 14 deletions(-)
--
2.44.0
Powered by blists - more mailing lists