[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211109090147.56978-1-likexu@tencent.com>
Date: Tue, 9 Nov 2021 17:01:47 +0800
From: Like Xu <like.xu.linux@...il.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>, Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] tools/perf/design: Synchronize the definition of enum perf_hw_id with code
From: Like Xu <likexu@...cent.com>
We're not surprised that there are tons of Linux users who
only read the documentation to learn about the kernel.
Let's update the perf part for common hardware events
since three new *generic* hardware events were added.
Signed-off-by: Like Xu <likexu@...cent.com>
---
tools/perf/design.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/design.txt b/tools/perf/design.txt
index a42fab308ff6..aa8cfeabb743 100644
--- a/tools/perf/design.txt
+++ b/tools/perf/design.txt
@@ -106,6 +106,9 @@ enum perf_hw_id {
PERF_COUNT_HW_BRANCH_INSTRUCTIONS = 4,
PERF_COUNT_HW_BRANCH_MISSES = 5,
PERF_COUNT_HW_BUS_CYCLES = 6,
+ PERF_COUNT_HW_STALLED_CYCLES_FRONTEND = 7,
+ PERF_COUNT_HW_STALLED_CYCLES_BACKEND = 8,
+ PERF_COUNT_HW_REF_CPU_CYCLES = 9,
};
These are standardized types of events that work relatively uniformly
--
2.33.0
Powered by blists - more mailing lists