linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Chu Guangqing <chuguangqing@inspur.com>
Cc: john.g.garry@oracle.com, will@kernel.org, james.clark@linaro.org,
	mike.leach@linaro.org, leo.yan@linux.dev, peterz@infradead.org,
	mingo@redhat.com, namhyung@kernel.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] perf vendor events arm64 AmpereOneX: Fix spelling typo in the metrics file
Date: Mon, 3 Nov 2025 17:33:20 -0300	[thread overview]
Message-ID: <aQkRkLMYTGLVJAuZ@x1> (raw)
In-Reply-To: <20251103014633.1213-2-chuguangqing@inspur.com>

On Mon, Nov 03, 2025 at 09:46:33AM +0800, Chu Guangqing wrote:
> The json file incorrectly used "acceses" instead of "accesses".

Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
 
> Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>
> ---
>  .../arch/arm64/ampere/ampereonex/metrics.json    | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
> index 6817cac149e0..a29aadc9b2e3 100644
> --- a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
> +++ b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
> @@ -388,55 +388,55 @@
>          "MetricExpr": "L1D_CACHE_RW / L1D_CACHE",
>          "BriefDescription": "L1D cache access - demand",
>          "MetricGroup": "Cache",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "l1d_cache_access_prefetches",
>          "MetricExpr": "L1D_CACHE_PRFM / L1D_CACHE",
>          "BriefDescription": "L1D cache access - prefetch",
>          "MetricGroup": "Cache",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "l1d_cache_demand_misses",
>          "MetricExpr": "L1D_CACHE_REFILL_RW / L1D_CACHE",
>          "BriefDescription": "L1D cache demand misses",
>          "MetricGroup": "Cache",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "l1d_cache_demand_misses_read",
>          "MetricExpr": "L1D_CACHE_REFILL_RD / L1D_CACHE",
>          "BriefDescription": "L1D cache demand misses - read",
>          "MetricGroup": "Cache",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "l1d_cache_demand_misses_write",
>          "MetricExpr": "L1D_CACHE_REFILL_WR / L1D_CACHE",
>          "BriefDescription": "L1D cache demand misses - write",
>          "MetricGroup": "Cache",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "l1d_cache_prefetch_misses",
>          "MetricExpr": "L1D_CACHE_REFILL_PRFM / L1D_CACHE",
>          "BriefDescription": "L1D cache prefetch misses",
>          "MetricGroup": "Cache",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "ase_scalar_mix",
>          "MetricExpr": "ASE_SCALAR_SPEC / OP_SPEC",
>          "BriefDescription": "Proportion of advanced SIMD data processing operations (excluding DP_SPEC/LD_SPEC) scalar operations",
>          "MetricGroup": "Instructions",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      },
>      {
>          "MetricName": "ase_vector_mix",
>          "MetricExpr": "ASE_VECTOR_SPEC / OP_SPEC",
>          "BriefDescription": "Proportion of advanced SIMD data processing operations (excluding DP_SPEC/LD_SPEC) vector operations",
>          "MetricGroup": "Instructions",
> -        "ScaleUnit": "100percent of cache acceses"
> +        "ScaleUnit": "100percent of cache accesses"
>      }
>  ]
> -- 
> 2.43.7
> 

      reply	other threads:[~2025-11-03 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  1:46 [PATCH v2 0/1] Fix spelling typo in tools/perf Chu Guangqing
2025-11-03  1:46 ` [PATCH v2 1/1] perf vendor events arm64 AmpereOneX: Fix spelling typo in the metrics file Chu Guangqing
2025-11-03 20:33   ` 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=aQkRkLMYTGLVJAuZ@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=chuguangqing@inspur.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).