From: John Garry <john.g.garry@oracle.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Kajol Jain <kjain@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf test: Fix "PMU event table sanity" for NO_JEVENTS=1
Date: Wed, 8 Mar 2023 09:58:16 +0000 [thread overview]
Message-ID: <eae0bd08-b18b-a9e2-ebc6-04c94534dfc3@oracle.com> (raw)
In-Reply-To: <20230308002714.1755698-1-irogers@google.com>
On 08/03/2023 00:27, Ian Rogers wrote:
> A table was renamed and needed to be renamed in the empty case.
>
> Fixes: 62774db2a05d ("perf jevents: Generate metrics and events as separate tables")
This looks ok, so:
Reviewed-by: John Garry <john.g.garry@oracle.com>
But a comment, below.
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/pmu-events/empty-pmu-events.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/pmu-events/empty-pmu-events.c b/tools/perf/pmu-events/empty-pmu-events.c
> index a938b74cf487..e74defb5284f 100644
> --- a/tools/perf/pmu-events/empty-pmu-events.c
> +++ b/tools/perf/pmu-events/empty-pmu-events.c
> @@ -227,7 +227,7 @@ static const struct pmu_events_map pmu_events_map[] = {
> },
> };
>
> -static const struct pmu_event pme_test_soc_sys[] = {
> +static const struct pmu_event pmu_events__test_soc_sys[] = {
Would it make sense or even possible to put these table names in macros
in a common header?
Thanks,
John
> {
> .name = "sys_ddr_pmu.write_cycles",
> .event = "event=0x2b",
> @@ -258,8 +258,8 @@ struct pmu_sys_events {
>
> static const struct pmu_sys_events pmu_sys_event_tables[] = {
> {
> - .table = { pme_test_soc_sys },
> - .name = "pme_test_soc_sys",
> + .table = { pmu_events__test_soc_sys },
> + .name = "pmu_events__test_soc_sys",
> },
> {
> .table = { 0 }
next prev parent reply other threads:[~2023-03-08 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 0:27 Ian Rogers
2023-03-08 9:58 ` John Garry [this message]
2023-03-14 11:43 ` Arnaldo Carvalho de Melo
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=eae0bd08-b18b-a9e2-ebc6-04c94534dfc3@oracle.com \
--to=john.g.garry@oracle.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®