mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kotaro Tokai (Fujitsu)" <fj0635gf@fujitsu.com>
To: 'James Clark' <james.clark@linaro.org>
Cc: John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
	Leo Yan <leo.yan@linux.dev>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] perf vendor events arm64: Update FUJITSU-MONAKA pmu event
Date: Thu, 19 Jun 2025 05:39:34 +0000	[thread overview]
Message-ID: <TY4PR01MB140068534B3D76C2CC7ED2C96DA7DA@TY4PR01MB14006.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <0060a6d7-ceee-4ecd-b4b7-1c9fc422efc7@linaro.org>



> 
> On 18/06/2025 7:35 am, Kotaro, Tokai wrote:
> > Update pmu events for FUJITSU-MONAKA.
> > And, also updated common-and-microarch.json.
> >
> > FUJITSU-MONAKA PMU Events Specification v1.1 and Errata v1.0 URL:
> > https://github.com/fujitsu/FUJITSU-MONAKA
> >
> > Arm Architecture Reference Version L.b URL:
> > https://developer.arm.com/documentation/ddi0487/lb/?lang=en
> >
> > Signed-off-by: Kotaro, Tokai <fj0635gf@aa.jp.fujitsu.com>
> > ---
> >   .../arch/arm64/common-and-microarch.json      | 70
> +++++++++++++
> >   .../arm64/fujitsu/monaka/core-imp-def.json    |  2 +-
> >   .../fujitsu/monaka/cycle_accounting.json      |  4 +-
> >   .../arch/arm64/fujitsu/monaka/exception.json  |  2 +-
> >   .../arm64/fujitsu/monaka/fp_operation.json    | 98
> +++++++++++++++----
> >   .../arch/arm64/fujitsu/monaka/l1d_cache.json  | 10 +-
> >   .../arch/arm64/fujitsu/monaka/l1i_cache.json  |  8 +-
> >   .../arch/arm64/fujitsu/monaka/l2_cache.json   | 28 +++---
> >   .../arch/arm64/fujitsu/monaka/l3_cache.json   | 63 ++++++------
> >   .../arch/arm64/fujitsu/monaka/ll_cache.json   |  2 +-
> >   .../arch/arm64/fujitsu/monaka/pipeline.json   |  6 +-
> >   .../arm64/fujitsu/monaka/spec_operation.json  | 12 +--
> >   .../arch/arm64/fujitsu/monaka/stall.json      |  4 +-
> >   .../arch/arm64/fujitsu/monaka/sve.json        | 44 ++++-----
> >   .../arch/arm64/fujitsu/monaka/tlb.json        | 56 +++++------
> >   15 files changed, 265 insertions(+), 144 deletions(-)
> >
> [...]
> > diff --git
> > a/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/fp_operation.json
> > b/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/fp_operation.json
> > index a3c368959199..2ffdc16530dd 100644
> > ---
> > a/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/fp_operation.json
> > +++ b/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/fp_operation.jso
> > +++ n
> > @@ -2,7 +2,7 @@
> >       {
> >           "EventCode": "0x0105",
> >           "EventName": "FP_MV_SPEC",
> > -        "BriefDescription": "This event counts architecturally executed
> floating-point move operations."
> > +        "BriefDescription": "This event counts architecturally executed
> floating-point move operation."
> 
> The original was more grammatically correct, but the updates are just from the pdf
> so:
> 
> Reviewed-by: James Clark <james.clark@linaro.org>
> 

Hi, James.

Thanks for the review!

Best regards,
Kotaro, Tokai

  reply	other threads:[~2025-06-19  5:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  6:35 Kotaro, Tokai
2025-06-18  8:28 ` James Clark
2025-06-19  5:39   ` Kotaro Tokai (Fujitsu) [this message]
2025-06-21 18:01 ` Namhyung Kim

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=TY4PR01MB140068534B3D76C2CC7ED2C96DA7DA@TY4PR01MB14006.jpnprd01.prod.outlook.com \
    --to=fj0635gf@fujitsu.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --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=leo.yan@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=will@kernel.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®