From: Ian Rogers <irogers@google.com>
To: John Garry <john.garry@huawei.com>
Cc: will@kernel.org, mathieu.poirier@linaro.org, leo.yan@linaro.org,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, zhangshaokun@hisilicon.com,
liuqi115@huawei.com
Subject: Re: [PATCH 4/5] perf test: Add pmu-event test for event described as "config="
Date: Tue, 28 Sep 2021 11:03:04 -0700 [thread overview]
Message-ID: <CAP-5=fVTd5g4=o84Tmo8Y45JDSWOL_RVhwBFCVVzV5HykW=GaQ@mail.gmail.com> (raw)
In-Reply-To: <1631795665-240946-5-git-send-email-john.garry@huawei.com>
On Thu, Sep 16, 2021 at 5:39 AM John Garry <john.garry@huawei.com> wrote:
>
> Add a new test event for a system event whose event member is in form
> "config=".
>
> Signed-off-by: John Garry <john.garry@huawei.com>
Acked-by: Ian Rogers <irogers@google.com>
Thanks,
Ian
> ---
> .../arch/test/test_soc/sys/uncore.json | 7 ++++++
> tools/perf/tests/pmu-events.c | 25 +++++++++++++++++++
> 2 files changed, 32 insertions(+)
>
> diff --git a/tools/perf/pmu-events/arch/test/test_soc/sys/uncore.json b/tools/perf/pmu-events/arch/test/test_soc/sys/uncore.json
> index 0f681a6e10ea..c7e7528db315 100644
> --- a/tools/perf/pmu-events/arch/test/test_soc/sys/uncore.json
> +++ b/tools/perf/pmu-events/arch/test/test_soc/sys/uncore.json
> @@ -6,4 +6,11 @@
> "Unit": "sys_ddr_pmu",
> "Compat": "v8"
> },
> + {
> + "BriefDescription": "ccn read-cycles event",
> + "ConfigCode": "0x2c",
> + "EventName": "sys_ccn_pmu.read_cycles",
> + "Unit": "sys_ccn_pmu",
> + "Compat": "0x01"
> + }
> ]
> diff --git a/tools/perf/tests/pmu-events.c b/tools/perf/tests/pmu-events.c
> index adfc17f51c7b..f14266a4c513 100644
> --- a/tools/perf/tests/pmu-events.c
> +++ b/tools/perf/tests/pmu-events.c
> @@ -208,8 +208,23 @@ static const struct perf_pmu_test_event sys_ddr_pmu_write_cycles = {
> .matching_pmu = "uncore_sys_ddr_pmu",
> };
>
> +static const struct perf_pmu_test_event sys_ccn_pmu_read_cycles = {
> + .event = {
> + .name = "sys_ccn_pmu.read_cycles",
> + .event = "config=0x2c",
> + .desc = "ccn read-cycles event. Unit: uncore_sys_ccn_pmu ",
> + .topic = "uncore",
> + .pmu = "uncore_sys_ccn_pmu",
> + .compat = "0x01",
> + },
> + .alias_str = "config=0x2c",
> + .alias_long_desc = "ccn read-cycles event. Unit: uncore_sys_ccn_pmu ",
> + .matching_pmu = "uncore_sys_ccn_pmu",
> +};
> +
> static const struct perf_pmu_test_event *sys_events[] = {
> &sys_ddr_pmu_write_cycles,
> + &sys_ccn_pmu_read_cycles,
> NULL
> };
>
> @@ -677,6 +692,16 @@ static struct perf_pmu_test_pmu test_pmus[] = {
> &sys_ddr_pmu_write_cycles,
> },
> },
> + {
> + .pmu = {
> + .name = (char *)"uncore_sys_ccn_pmu4",
> + .is_uncore = 1,
> + .id = (char *)"0x01",
> + },
> + .aliases = {
> + &sys_ccn_pmu_read_cycles,
> + },
> + },
> };
>
> /* Test that aliases generated are as expected */
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-09-28 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 12:34 [PATCH 0/5] Improve perf list support for hisi uncore PMUs John Garry
2021-09-16 12:34 ` [PATCH 1/5] perf parse-events: Set numeric term config John Garry
2021-09-28 17:59 ` Ian Rogers
2021-09-28 19:16 ` Arnaldo Carvalho de Melo
2021-09-16 12:34 ` [PATCH 2/5] perf jevents: Support ConfigCode John Garry
2021-09-28 18:00 ` Ian Rogers
2021-09-16 12:34 ` [PATCH 3/5] perf test: Verify more event members in pmu-events test John Garry
2021-09-28 18:02 ` Ian Rogers
2021-09-16 12:34 ` [PATCH 4/5] perf test: Add pmu-event test for event described as "config=" John Garry
2021-09-28 18:03 ` Ian Rogers [this message]
2021-09-16 12:34 ` [PATCH 5/5] perf vendor events arm64: Revise hip08 uncore events John Garry
2021-09-28 18:04 ` Ian Rogers
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='CAP-5=fVTd5g4=o84Tmo8Y45JDSWOL_RVhwBFCVVzV5HykW=GaQ@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuqi115@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.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).