From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
John Garry <john.g.garry@oracle.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Xu Yang <xu.yang_2@nxp.com>, Sandipan Das <sandipan.das@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
philip.li@intel.com, oliver.sang@intel.com,
Weilin Wang <weilin.wang@intel.com>
Subject: Re: [PATCH v3 0/2] perf jevents: Autogenerate empty-pmu-events.c
Date: Wed, 31 Jul 2024 10:05:05 -0300 [thread overview]
Message-ID: <Zqo2gfaQ96WkrZMH@x1> (raw)
In-Reply-To: <20240730191744.3097329-1-irogers@google.com>
On Tue, Jul 30, 2024 at 12:17:42PM -0700, Ian Rogers wrote:
> Rebase of v2 patch set on tmp.perf-tools-next.
> https://lore.kernel.org/lkml/20240525013021.436430-1-irogers@google.com/
>
> Review was delayed because of an Intel automatic testing issue,
> confirmed not an issue here:
> https://lore.kernel.org/lkml/ZqhGNm+WDcsNx05e@xsang-OptiPlex-9020/
Thanks, applied to tmp.perf-tools-next,
- Arnaldo
> v3: Rebase and add John Garry's reviewed-by tag.
> v2: Add not found constant.
> Ian Rogers (2):
> perf jevents: Use name for special find value
> perf jevents: Autogenerate empty-pmu-events.c
>
> tools/perf/Makefile.perf | 2 +
> tools/perf/pmu-events/Build | 12 +-
> tools/perf/pmu-events/empty-pmu-events.c | 894 ++++++++++++++---------
> tools/perf/pmu-events/jevents.py | 12 +-
> tools/perf/pmu-events/pmu-events.h | 9 +
> 5 files changed, 574 insertions(+), 355 deletions(-)
>
> --
> 2.46.0.rc2.264.g509ed76dc8-goog
prev parent reply other threads:[~2024-07-31 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 19:17 [PATCH v3 0/2] perf jevents: Autogenerate empty-pmu-events.c Ian Rogers
2024-07-30 19:17 ` [PATCH v3 1/2] perf jevents: Use name for special find value Ian Rogers
2024-07-31 13:19 ` Arnaldo Carvalho de Melo
2024-07-30 19:17 ` [PATCH v3 2/2] perf jevents: Autogenerate empty-pmu-events.c Ian Rogers
2024-07-31 13:18 ` Arnaldo Carvalho de Melo
2024-07-31 14:08 ` Ian Rogers
2024-07-31 15:33 ` Arnaldo Carvalho de Melo
2024-07-31 15:46 ` Arnaldo Carvalho de Melo
2024-07-31 15:58 ` Ian Rogers
2024-07-31 18:53 ` Arnaldo Carvalho de Melo
2024-07-31 20:20 ` Ian Rogers
2024-07-31 20:41 ` Arnaldo Carvalho de Melo
2024-08-01 1:35 ` Ian Rogers
2024-07-31 13:05 ` Arnaldo Carvalho de Melo [this message]
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=Zqo2gfaQ96WkrZMH@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.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=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=philip.li@intel.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=sandipan.das@amd.com \
--cc=weilin.wang@intel.com \
--cc=xu.yang_2@nxp.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).