[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221129111946.409-1-ravi.bangoria@amd.com>
Date: Tue, 29 Nov 2022 16:49:44 +0530
From: Ravi Bangoria <ravi.bangoria@....com>
To: <acme@...nel.org>
CC: <ravi.bangoria@....com>, <irogers@...gle.com>, <jolsa@...hat.com>,
<namhyung@...nel.org>, <peterz@...radead.org>,
<mark.rutland@....com>, <kan.liang@...ux.intel.com>,
<adrian.hunter@...el.com>, <alexander.shishkin@...ux.intel.com>,
<carsten.haitzler@....com>, <leo.yan@...aro.org>,
<maddy@...ux.ibm.com>, <kjain@...ux.ibm.com>,
<atrajeev@...ux.vnet.ibm.com>, <tmricht@...ux.ibm.com>,
<linux-perf-users@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<sandipan.das@....com>, <ananth.narayan@....com>,
<santosh.shukla@....com>
Subject: [PATCH v2 0/2] perf test: Add event group test
Multiple events in a group can belong to one or more pmus, however
there are some limitations to it. One of the limitation is, perf
doesn't allow creating a group of events from different hw pmus.
Write a simple test to create various combinations of hw, sw and
uncore pmu events and verify group creation succeeds or fails as
expected.
v1: https://lore.kernel.org/r/20221125032018.962-1-ravi.bangoria@amd.com
v1->v2:
- #1 is new. It makes pmus list variable non-static and moves
it to a new file.
- Instead of hardcoded uncore pmu configuration, iterate over
pmus list and use whichever first uncore pmu is available.
Ravi Bangoria (2):
perf tool: Move pmus list variable to new a file
perf test: Add event group test
tools/perf/tests/Build | 1 +
tools/perf/tests/builtin-test.c | 1 +
tools/perf/tests/event_groups.c | 109 ++++++++++++++++++++++++++++++++
tools/perf/tests/tests.h | 1 +
tools/perf/util/Build | 1 +
tools/perf/util/pmu.c | 2 +-
tools/perf/util/pmus.c | 5 ++
tools/perf/util/pmus.h | 9 +++
8 files changed, 128 insertions(+), 1 deletion(-)
create mode 100644 tools/perf/tests/event_groups.c
create mode 100644 tools/perf/util/pmus.c
create mode 100644 tools/perf/util/pmus.h
--
2.38.1
Powered by blists - more mailing lists