Re: [PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes

From: Ian Rogers
Date: Thu Aug 24 2023 - 16:38:00 EST

Next message: Colin King (gmail): "Re: [PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes"
Previous message: Willem de Bruijn: "Re: [PATCH v2 2/2] selftests/net: replace ternary operator with min()/max()"
In reply to: Ian Rogers: "[PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes"
Next in thread: Colin King (gmail): "Re: [PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Aug 24, 2023 at 1:24 PM Ian Rogers <irogers@xxxxxxxxxx> wrote:
>
> Update perf json files with spelling fixes by Colin Ian King
> <colin.i.king@xxxxxxxxx> contributed in:
> https://github.com/intel/perfmon/pull/96
> Fix various spelling mistakes and typos as found using codespell #96
>
> Signed-off-by: Ian Rogers <irogers@xxxxxxxxxx>

I think it would be more correct here if Colin Ian King
<colin.i.king@xxxxxxxxx> were the author here. I generated the changes
from their work and they posted similar changes to LKML in the past.
I'm not sure what the policy is, and I didn't have Colin's permission
to list them as author, but it'd feel more correct to me for the
author to be changed.

Thanks,
Ian

> ---
> .../arch/x86/alderlake/adl-metrics.json | 6 +++---
> .../arch/x86/alderlake/pipeline.json | 2 +-
> .../arch/x86/alderlaken/adln-metrics.json | 6 +++---
> .../x86/broadwellde/uncore-interconnect.json | 18 +++++++++---------
> .../x86/broadwellx/uncore-interconnect.json | 18 +++++++++---------
> .../pmu-events/arch/x86/haswell/memory.json | 2 +-
> .../pmu-events/arch/x86/haswellx/memory.json | 2 +-
> .../arch/x86/haswellx/uncore-interconnect.json | 18 +++++++++---------
> .../arch/x86/ivytown/uncore-interconnect.json | 18 +++++++++---------
> .../arch/x86/jaketown/uncore-interconnect.json | 18 +++++++++---------
> .../arch/x86/nehalemep/floating-point.json | 2 +-
> .../arch/x86/nehalemex/floating-point.json | 2 +-
> .../arch/x86/westmereep-dp/floating-point.json | 2 +-
> .../arch/x86/westmereep-sp/floating-point.json | 2 +-
> .../arch/x86/westmereex/floating-point.json | 2 +-
> 15 files changed, 59 insertions(+), 59 deletions(-)
>
> diff --git a/tools/perf/pmu-events/arch/x86/alderlake/adl-metrics.json b/tools/perf/pmu-events/arch/x86/alderlake/adl-metrics.json
> index c6780d5c456b..8b6bed3bc766 100644
> --- a/tools/perf/pmu-events/arch/x86/alderlake/adl-metrics.json
> +++ b/tools/perf/pmu-events/arch/x86/alderlake/adl-metrics.json
> @@ -395,13 +395,13 @@
> "Unit": "cpu_atom"
> },
> {
> - "BriefDescription": "Instructions per Branch (lower number means higher occurance rate)",
> + "BriefDescription": "Instructions per Branch (lower number means higher occurrence rate)",
> "MetricExpr": "INST_RETIRED.ANY / BR_INST_RETIRED.ALL_BRANCHES",
> "MetricName": "tma_info_inst_mix_ipbranch",
> "Unit": "cpu_atom"
> },
> {
> - "BriefDescription": "Instruction per (near) call (lower number means higher occurance rate)",
> + "BriefDescription": "Instruction per (near) call (lower number means higher occurrence rate)",
> "MetricExpr": "INST_RETIRED.ANY / BR_INST_RETIRED.CALL",
> "MetricName": "tma_info_inst_mix_ipcall",
> "Unit": "cpu_atom"
> @@ -726,7 +726,7 @@
> "Unit": "cpu_atom"
> },
> {
> - "BriefDescription": "Counts the numer of issue slots that result in retirement slots.",
> + "BriefDescription": "Counts the number of issue slots that result in retirement slots.",
> "DefaultMetricgroupName": "TopdownL1",
> "MetricExpr": "TOPDOWN_RETIRING.ALL / tma_info_core_slots",
> "MetricGroup": "Default;TopdownL1;tma_L1_group",
> diff --git a/tools/perf/pmu-events/arch/x86/alderlake/pipeline.json b/tools/perf/pmu-events/arch/x86/alderlake/pipeline.json
> index cb5b8611064b..a92013cdf136 100644
> --- a/tools/perf/pmu-events/arch/x86/alderlake/pipeline.json
> +++ b/tools/perf/pmu-events/arch/x86/alderlake/pipeline.json
> @@ -1145,7 +1145,7 @@
> "BriefDescription": "TMA slots wasted due to incorrect speculation by branch mispredictions",
> "EventCode": "0xa4",
> "EventName": "TOPDOWN.BR_MISPREDICT_SLOTS",
> - "PublicDescription": "Number of TMA slots that were wasted due to incorrect speculation by (any type of) branch mispredictions. This event estimates number of specualtive operations that were issued but not retired as well as the out-of-order engine recovery past a branch misprediction.",
> + "PublicDescription": "Number of TMA slots that were wasted due to incorrect speculation by (any type of) branch mispredictions. This event estimates number of speculative operations that were issued but not retired as well as the out-of-order engine recovery past a branch misprediction.",
> "SampleAfterValue": "10000003",
> "UMask": "0x8",
> "Unit": "cpu_core"
> diff --git a/tools/perf/pmu-events/arch/x86/alderlaken/adln-metrics.json b/tools/perf/pmu-events/arch/x86/alderlaken/adln-metrics.json
> index 06e67e34e1bf..c150c14ac6ed 100644
> --- a/tools/perf/pmu-events/arch/x86/alderlaken/adln-metrics.json
> +++ b/tools/perf/pmu-events/arch/x86/alderlaken/adln-metrics.json
> @@ -328,12 +328,12 @@
> "MetricName": "tma_info_inst_mix_idiv_uop_ratio"
> },
> {
> - "BriefDescription": "Instructions per Branch (lower number means higher occurance rate)",
> + "BriefDescription": "Instructions per Branch (lower number means higher occurrence rate)",
> "MetricExpr": "INST_RETIRED.ANY / BR_INST_RETIRED.ALL_BRANCHES",
> "MetricName": "tma_info_inst_mix_ipbranch"
> },
> {
> - "BriefDescription": "Instruction per (near) call (lower number means higher occurance rate)",
> + "BriefDescription": "Instruction per (near) call (lower number means higher occurrence rate)",
> "MetricExpr": "INST_RETIRED.ANY / BR_INST_RETIRED.CALL",
> "MetricName": "tma_info_inst_mix_ipcall"
> },
> @@ -616,7 +616,7 @@
> "ScaleUnit": "100%"
> },
> {
> - "BriefDescription": "Counts the numer of issue slots that result in retirement slots.",
> + "BriefDescription": "Counts the number of issue slots that result in retirement slots.",
> "DefaultMetricgroupName": "TopdownL1",
> "MetricExpr": "TOPDOWN_RETIRING.ALL / tma_info_core_slots",
> "MetricGroup": "Default;TopdownL1;tma_L1_group",
> diff --git a/tools/perf/pmu-events/arch/x86/broadwellde/uncore-interconnect.json b/tools/perf/pmu-events/arch/x86/broadwellde/uncore-interconnect.json
> index 8a327e0f1441..910395977a6e 100644
> --- a/tools/perf/pmu-events/arch/x86/broadwellde/uncore-interconnect.json
> +++ b/tools/perf/pmu-events/arch/x86/broadwellde/uncore-interconnect.json
> @@ -253,7 +253,7 @@
> "EventCode": "0x4",
> "EventName": "UNC_I_RxR_BL_DRS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -261,7 +261,7 @@
> "EventCode": "0x1",
> "EventName": "UNC_I_RxR_BL_DRS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -269,7 +269,7 @@
> "EventCode": "0x7",
> "EventName": "UNC_I_RxR_BL_DRS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -277,7 +277,7 @@
> "EventCode": "0x5",
> "EventName": "UNC_I_RxR_BL_NCB_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -285,7 +285,7 @@
> "EventCode": "0x2",
> "EventName": "UNC_I_RxR_BL_NCB_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -293,7 +293,7 @@
> "EventCode": "0x8",
> "EventName": "UNC_I_RxR_BL_NCB_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -301,7 +301,7 @@
> "EventCode": "0x6",
> "EventName": "UNC_I_RxR_BL_NCS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -309,7 +309,7 @@
> "EventCode": "0x3",
> "EventName": "UNC_I_RxR_BL_NCS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -317,7 +317,7 @@
> "EventCode": "0x9",
> "EventName": "UNC_I_RxR_BL_NCS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> diff --git a/tools/perf/pmu-events/arch/x86/broadwellx/uncore-interconnect.json b/tools/perf/pmu-events/arch/x86/broadwellx/uncore-interconnect.json
> index e61a23f68899..b9fb216bee16 100644
> --- a/tools/perf/pmu-events/arch/x86/broadwellx/uncore-interconnect.json
> +++ b/tools/perf/pmu-events/arch/x86/broadwellx/uncore-interconnect.json
> @@ -271,7 +271,7 @@
> "EventCode": "0x4",
> "EventName": "UNC_I_RxR_BL_DRS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -279,7 +279,7 @@
> "EventCode": "0x1",
> "EventName": "UNC_I_RxR_BL_DRS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -287,7 +287,7 @@
> "EventCode": "0x7",
> "EventName": "UNC_I_RxR_BL_DRS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -295,7 +295,7 @@
> "EventCode": "0x5",
> "EventName": "UNC_I_RxR_BL_NCB_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -303,7 +303,7 @@
> "EventCode": "0x2",
> "EventName": "UNC_I_RxR_BL_NCB_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -311,7 +311,7 @@
> "EventCode": "0x8",
> "EventName": "UNC_I_RxR_BL_NCB_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -319,7 +319,7 @@
> "EventCode": "0x6",
> "EventName": "UNC_I_RxR_BL_NCS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -327,7 +327,7 @@
> "EventCode": "0x3",
> "EventName": "UNC_I_RxR_BL_NCS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -335,7 +335,7 @@
> "EventCode": "0x9",
> "EventName": "UNC_I_RxR_BL_NCS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> diff --git a/tools/perf/pmu-events/arch/x86/haswell/memory.json b/tools/perf/pmu-events/arch/x86/haswell/memory.json
> index 2fc25e22a42a..df44c28efeeb 100644
> --- a/tools/perf/pmu-events/arch/x86/haswell/memory.json
> +++ b/tools/perf/pmu-events/arch/x86/haswell/memory.json
> @@ -62,7 +62,7 @@
> "BriefDescription": "Counts the number of machine clears due to memory order conflicts.",
> "EventCode": "0xC3",
> "EventName": "MACHINE_CLEARS.MEMORY_ORDERING",
> - "PublicDescription": "This event counts the number of memory ordering machine clears detected. Memory ordering machine clears can result from memory address aliasing or snoops from another hardware thread or core to data inflight in the pipeline. Machine clears can have a significant performance impact if they are happening frequently.",
> + "PublicDescription": "This event counts the number of memory ordering machine clears detected. Memory ordering machine clears can result from memory address aliasing or snoops from another hardware thread or core to data in-flight in the pipeline. Machine clears can have a significant performance impact if they are happening frequently.",
> "SampleAfterValue": "100003",
> "UMask": "0x2"
> },
> diff --git a/tools/perf/pmu-events/arch/x86/haswellx/memory.json b/tools/perf/pmu-events/arch/x86/haswellx/memory.json
> index 2d212cf59e92..d66e465ce41a 100644
> --- a/tools/perf/pmu-events/arch/x86/haswellx/memory.json
> +++ b/tools/perf/pmu-events/arch/x86/haswellx/memory.json
> @@ -62,7 +62,7 @@
> "BriefDescription": "Counts the number of machine clears due to memory order conflicts.",
> "EventCode": "0xC3",
> "EventName": "MACHINE_CLEARS.MEMORY_ORDERING",
> - "PublicDescription": "This event counts the number of memory ordering machine clears detected. Memory ordering machine clears can result from memory address aliasing or snoops from another hardware thread or core to data inflight in the pipeline. Machine clears can have a significant performance impact if they are happening frequently.",
> + "PublicDescription": "This event counts the number of memory ordering machine clears detected. Memory ordering machine clears can result from memory address aliasing or snoops from another hardware thread or core to data in-flight in the pipeline. Machine clears can have a significant performance impact if they are happening frequently.",
> "SampleAfterValue": "100003",
> "UMask": "0x2"
> },
> diff --git a/tools/perf/pmu-events/arch/x86/haswellx/uncore-interconnect.json b/tools/perf/pmu-events/arch/x86/haswellx/uncore-interconnect.json
> index 954e8198c7a5..bef1f5ef6f31 100644
> --- a/tools/perf/pmu-events/arch/x86/haswellx/uncore-interconnect.json
> +++ b/tools/perf/pmu-events/arch/x86/haswellx/uncore-interconnect.json
> @@ -271,7 +271,7 @@
> "EventCode": "0x4",
> "EventName": "UNC_I_RxR_BL_DRS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -279,7 +279,7 @@
> "EventCode": "0x1",
> "EventName": "UNC_I_RxR_BL_DRS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -287,7 +287,7 @@
> "EventCode": "0x7",
> "EventName": "UNC_I_RxR_BL_DRS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -295,7 +295,7 @@
> "EventCode": "0x5",
> "EventName": "UNC_I_RxR_BL_NCB_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -303,7 +303,7 @@
> "EventCode": "0x2",
> "EventName": "UNC_I_RxR_BL_NCB_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -311,7 +311,7 @@
> "EventCode": "0x8",
> "EventName": "UNC_I_RxR_BL_NCB_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -319,7 +319,7 @@
> "EventCode": "0x6",
> "EventName": "UNC_I_RxR_BL_NCS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -327,7 +327,7 @@
> "EventCode": "0x3",
> "EventName": "UNC_I_RxR_BL_NCS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -335,7 +335,7 @@
> "EventCode": "0x9",
> "EventName": "UNC_I_RxR_BL_NCS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> diff --git a/tools/perf/pmu-events/arch/x86/ivytown/uncore-interconnect.json b/tools/perf/pmu-events/arch/x86/ivytown/uncore-interconnect.json
> index ccf451534d16..f4d11da01383 100644
> --- a/tools/perf/pmu-events/arch/x86/ivytown/uncore-interconnect.json
> +++ b/tools/perf/pmu-events/arch/x86/ivytown/uncore-interconnect.json
> @@ -140,7 +140,7 @@
> "EventCode": "0x4",
> "EventName": "UNC_I_RxR_BL_DRS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -148,21 +148,21 @@
> "EventCode": "0x1",
> "EventName": "UNC_I_RxR_BL_DRS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x7",
> "EventName": "UNC_I_RxR_BL_DRS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x5",
> "EventName": "UNC_I_RxR_BL_NCB_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -170,21 +170,21 @@
> "EventCode": "0x2",
> "EventName": "UNC_I_RxR_BL_NCB_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x8",
> "EventName": "UNC_I_RxR_BL_NCB_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x6",
> "EventName": "UNC_I_RxR_BL_NCS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -192,14 +192,14 @@
> "EventCode": "0x3",
> "EventName": "UNC_I_RxR_BL_NCS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x9",
> "EventName": "UNC_I_RxR_BL_NCS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> diff --git a/tools/perf/pmu-events/arch/x86/jaketown/uncore-interconnect.json b/tools/perf/pmu-events/arch/x86/jaketown/uncore-interconnect.json
> index 874f15ea8228..0fc907e5cf3c 100644
> --- a/tools/perf/pmu-events/arch/x86/jaketown/uncore-interconnect.json
> +++ b/tools/perf/pmu-events/arch/x86/jaketown/uncore-interconnect.json
> @@ -140,7 +140,7 @@
> "EventCode": "0x4",
> "EventName": "UNC_I_RxR_BL_DRS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -148,21 +148,21 @@
> "EventCode": "0x1",
> "EventName": "UNC_I_RxR_BL_DRS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x7",
> "EventName": "UNC_I_RxR_BL_DRS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x5",
> "EventName": "UNC_I_RxR_BL_NCB_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -170,21 +170,21 @@
> "EventCode": "0x2",
> "EventName": "UNC_I_RxR_BL_NCB_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x8",
> "EventName": "UNC_I_RxR_BL_NCB_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x6",
> "EventName": "UNC_I_RxR_BL_NCS_CYCLES_FULL",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> @@ -192,14 +192,14 @@
> "EventCode": "0x3",
> "EventName": "UNC_I_RxR_BL_NCS_INSERTS",
> "PerPkg": "1",
> - "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> "EventCode": "0x9",
> "EventName": "UNC_I_RxR_BL_NCS_OCCUPANCY",
> "PerPkg": "1",
> - "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requets as well as outbound MMIO writes.",
> + "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
> "Unit": "IRP"
> },
> {
> diff --git a/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json b/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json
> index c03f8990fa82..196ae1d9b157 100644
> --- a/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json
> +++ b/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json
> @@ -8,7 +8,7 @@
> "UMask": "0x1"
> },
> {
> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)",
> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)",
> "EventCode": "0xF7",
> "EventName": "FP_ASSIST.INPUT",
> "PEBS": "1",
> diff --git a/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json b/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json
> index c03f8990fa82..196ae1d9b157 100644
> --- a/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json
> +++ b/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json
> @@ -8,7 +8,7 @@
> "UMask": "0x1"
> },
> {
> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)",
> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)",
> "EventCode": "0xF7",
> "EventName": "FP_ASSIST.INPUT",
> "PEBS": "1",
> diff --git a/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json
> index c03f8990fa82..196ae1d9b157 100644
> --- a/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json
> +++ b/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json
> @@ -8,7 +8,7 @@
> "UMask": "0x1"
> },
> {
> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)",
> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)",
> "EventCode": "0xF7",
> "EventName": "FP_ASSIST.INPUT",
> "PEBS": "1",
> diff --git a/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json
> index c03f8990fa82..196ae1d9b157 100644
> --- a/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json
> +++ b/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json
> @@ -8,7 +8,7 @@
> "UMask": "0x1"
> },
> {
> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)",
> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)",
> "EventCode": "0xF7",
> "EventName": "FP_ASSIST.INPUT",
> "PEBS": "1",
> diff --git a/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
> index c03f8990fa82..196ae1d9b157 100644
> --- a/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
> +++ b/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
> @@ -8,7 +8,7 @@
> "UMask": "0x1"
> },
> {
> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)",
> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)",
> "EventCode": "0xF7",
> "EventName": "FP_ASSIST.INPUT",
> "PEBS": "1",
> --
> 2.42.0.rc2.253.gd59a3bf2b4-goog
>

Next message: Colin King (gmail): "Re: [PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes"
Previous message: Willem de Bruijn: "Re: [PATCH v2 2/2] selftests/net: replace ternary operator with min()/max()"
In reply to: Ian Rogers: "[PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes"
Next in thread: Colin King (gmail): "Re: [PATCH v1 2/2] perf vendor events intel: Fix spelling mistakes"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]