From: Namhyung Kim <namhyung@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: Frank.li@nxp.com, will@kernel.org, mark.rutland@arm.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
john.g.garry@oracle.com, james.clark@linaro.org,
mike.leach@linaro.org, leo.yan@linux.dev, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/3] perf vendor events arm64: Add i.MX91 DDR Performance Monitor metrics
Date: Wed, 9 Oct 2024 17:21:33 -0700 [thread overview]
Message-ID: <ZwceDV3xNXijFF_8@google.com> (raw)
In-Reply-To: <20241009093750.6mbq3zkmupahrzmm@hippo>
On Wed, Oct 09, 2024 at 05:38:25PM +0800, Xu Yang wrote:
> On Tue, Oct 08, 2024 at 11:49:23PM -0700, Namhyung Kim wrote:
> > On Tue, Oct 08, 2024 at 01:49:35PM +0800, Xu Yang wrote:
> > > Hi Namhyung,
> > >
> > > On Mon, Sep 30, 2024 at 02:07:51PM -0700, Namhyung Kim wrote:
> > > > Hello,
> > > >
> > > > On Tue, Sep 24, 2024 at 02:12:51PM +0800, Xu Yang wrote:
> > > > > Add JSON metrics for i.MX91 DDR Performance Monitor.
> > > > >
> > > > > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > > > > ---
> > > > > .../arch/arm64/freescale/imx91/sys/ddrc.json | 9 +++++++
> > > > > .../arm64/freescale/imx91/sys/metrics.json | 26 +++++++++++++++++++
> > > > > 2 files changed, 35 insertions(+)
> > > > > create mode 100644 tools/perf/pmu-events/arch/arm64/freescale/imx91/sys/ddrc.json
> > > > > create mode 100644 tools/perf/pmu-events/arch/arm64/freescale/imx91/sys/metrics.json
> > > >
> > > > How do you want to route this? As it's mixed with kernel changes, I
> > > > would generally request to split but it's a change just to add new
> > > > files so it should be ok to go with other tree. In that case,
> > >
> > > Sorry for late.
> > >
> > > How about you pick up this one to perf-tools tree and Will Deacon pick up
> > > the first 2 patches to his tree? I didn't see Will apply perf-tools patch
> > > before.
> >
> > Did Will pick up the kernel patches already?
>
> Not yet. I could ping you once it's done, is it ok?
Sure!
Thanks,
Namhyung
next prev parent reply other threads:[~2024-10-10 0:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 6:12 [PATCH 1/3] dt-bindings: perf: fsl-imx-ddr: Add i.MX91 compatible Xu Yang
2024-09-24 6:12 ` [PATCH 2/3] perf: imx_perf: add support for i.MX91 platform Xu Yang
2024-09-24 18:09 ` Frank Li
2024-09-24 6:12 ` [PATCH 3/3] perf vendor events arm64: Add i.MX91 DDR Performance Monitor metrics Xu Yang
2024-09-30 21:07 ` Namhyung Kim
2024-10-08 5:49 ` Xu Yang
2024-10-09 6:49 ` Namhyung Kim
2024-10-09 9:38 ` Xu Yang
2024-10-10 0:21 ` Namhyung Kim [this message]
2024-10-29 8:31 ` Xu Yang
2024-10-24 12:26 ` Will Deacon
2024-10-29 18:29 ` Namhyung Kim
2024-09-24 16:27 ` [PATCH 1/3] dt-bindings: perf: fsl-imx-ddr: Add i.MX91 compatible Conor Dooley
2024-10-09 17:42 ` Frank Li
2024-10-24 12:25 ` Will Deacon
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=ZwceDV3xNXijFF_8@google.com \
--to=namhyung@kernel.org \
--cc=Frank.li@nxp.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
--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).