From: Ravi Bangoria <ravi.bangoria@amd.com>
To: <acme@kernel.org>
Cc: <ravi.bangoria@amd.com>, <irogers@google.com>, <jolsa@redhat.com>,
<namhyung@kernel.org>, <peterz@infradead.org>,
<mark.rutland@arm.com>, <kan.liang@linux.intel.com>,
<adrian.hunter@intel.com>, <alexander.shishkin@linux.intel.com>,
<carsten.haitzler@arm.com>, <leo.yan@linaro.org>,
<maddy@linux.ibm.com>, <kjain@linux.ibm.com>,
<atrajeev@linux.vnet.ibm.com>, <tmricht@linux.ibm.com>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <sandipan.das@amd.com>,
<ananth.narayan@amd.com>, <santosh.shukla@amd.com>
Subject: [PATCH v2 0/2] perf test: Add event group test
Date: Tue, 29 Nov 2022 16:49:44 +0530 [thread overview]
Message-ID: <20221129111946.409-1-ravi.bangoria@amd.com> (raw)
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
next reply other threads:[~2022-11-29 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 11:19 Ravi Bangoria [this message]
2022-11-29 11:19 ` [PATCH v2 1/2] perf tool: Move pmus list variable to new a file Ravi Bangoria
2022-11-29 11:19 ` [PATCH v2 2/2] perf test: Add event group test Ravi Bangoria
2022-11-29 20:13 ` Liang, Kan
2022-12-01 9:13 ` Ravi Bangoria
2022-12-01 14:02 ` Liang, Kan
2022-12-01 15:29 ` Ravi Bangoria
2022-12-01 15:47 ` Liang, Kan
2022-12-01 16:29 ` Ravi Bangoria
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=20221129111946.409-1-ravi.bangoria@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=carsten.haitzler@arm.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tmricht@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).