Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3B096C433F5 for ; Mon, 3 Jan 2022 01:02:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231276AbiACBCJ (ORCPT ); Sun, 2 Jan 2022 20:02:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32788 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231245AbiACBCH (ORCPT ); Sun, 2 Jan 2022 20:02:07 -0500 Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CC9FCC061761 for ; Sun, 2 Jan 2022 17:02:06 -0800 (PST) Received: by mail-io1-xd2f.google.com with SMTP id o7so36862191ioo.9 for ; Sun, 02 Jan 2022 17:02:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=LCdYBCWRZKdKiGE+rth1UGOefg7aXgJUkI8QK9WTTv0=; b=cAnHpedkcbG2/TODtq8Y49qZngzDR+QwicjNn+xyAbor0nPTj6CXPXkVt5w7RshrH0 kz9Lcfe/6UdlkB9xoQ0IFMiTNwOoObqwCnrmrvY4nzQw35pKvZPmS/0/ckzK8MdX6mV5 y7W4f0dJuYyXcJd3w2bDnicHbyu57Bmt/TbNn1RxU9ycpr2KUtv88wMjm4GOaQwMf00/ PRpfD8+t7kx20/8NLIO3DvktxI8g4b/+FA3MFJ2sUb0/3fPw6lNnH+lcD2XNeDg5hedN qpqerZmbZhIgqv1FXDq7x4LMEgOo2EXdy5vtw0z3cWtGZwOYXBDazIh3XDo6NOHFxGvw O5lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=LCdYBCWRZKdKiGE+rth1UGOefg7aXgJUkI8QK9WTTv0=; b=h4l6vXwdhoUHYl4EmH5gBZjPpSoGkcpdSLvucHgg5eaLjTPz0VJVRXdf55wdZW3WTv nJ2emLzVHoU7THRntzfICNGInyCIU4UxntnDmNlhosB9j5zyUwNXqE7a+BZPCM1loMi6 px1nfS1eLp4o67PUjEfnEbI9GpWxne/mzq87neNdxIW5qDYv9E/rHyfWpgjwUVu7Gyd1 vkKBm6yA4JU1YpEYdaiXcr2EfSMINQSEYvDWg2mDtZeZO5JsdQ1Gv3rzbkNQG9LsPGC8 YRSBwlkJ9w+fpeQ3Q8gnhHRljZ/3Od/gNtB0XUnnXnhcnCUb2naMkIo8mj0MkeCswq3q 8YaQ== X-Gm-Message-State: AOAM531KqZvACwaZ8iqyjHkB08UjOSVMg4KrQypl7akFMpf4erH3F8SX +pwbB3CXrv6nuzWTiV+o/3nsSCndrZdMF2/sLv8i/w== X-Google-Smtp-Source: ABdhPJyMLyEB8QQhyG6sPL+tCsTDM7rfRr6HtT20LsS+F4EAzutQwYFbATydUR8ILFuU+KywV4LCkEdYtMBfuRd2ayI= X-Received: by 2002:a05:6602:1484:: with SMTP id a4mr19570511iow.35.1641171725930; Sun, 02 Jan 2022 17:02:05 -0800 (PST) MIME-Version: 1.0 References: <20211226025215.22866-1-rdunlap@infradead.org> In-Reply-To: <20211226025215.22866-1-rdunlap@infradead.org> From: Ian Rogers Date: Sun, 2 Jan 2022 17:01:53 -0800 Message-ID: Subject: Re: [PATCH] perf: fix typos of "its" and "reponse" To: Randy Dunlap , Andi Kleen , "zhengjun.xing@intel.com" Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , linux-perf-users@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 25, 2021 at 6:52 PM Randy Dunlap wrote: > > Use the possessive "its" instead of the contraction of "it is" ("it's") > where needed in user-viewable messages. > > Correct typos of "reponse" to "response" (reported by checkpatch). > > Signed-off-by: Randy Dunlap > Cc: Peter Zijlstra > Cc: Ingo Molnar > Cc: Arnaldo Carvalho de Melo > Cc: Mark Rutland > Cc: Alexander Shishkin > Cc: Jiri Olsa > Cc: Namhyung Kim > Cc: linux-perf-users@vger.kernel.org Making this information better is valuable! The data is autogenerated by these scripts: https://github.com/intel/event-converter-for-linux-perf From data here: https://download.01.org/perfmon/ In a way the files that are in the tree are temporary build files. Perhaps we can have the original source and scripts within the Linux tools tree to simplify fixes like these. Thanks, Ian > --- > tools/perf/pmu-events/arch/x86/broadwell/uncore.json | 6 +++= --- > tools/perf/pmu-events/arch/x86/cascadelakex/uncore-other.json | 4 ++-= - > tools/perf/pmu-events/arch/x86/haswell/uncore.json | 6 +++= --- > tools/perf/pmu-events/arch/x86/skylakex/uncore-other.json | 4 ++-= - > 4 files changed, 10 insertions(+), 10 deletions(-) > > --- linux-next-20211224.orig/tools/perf/pmu-events/arch/x86/broadwell/unc= ore.json > +++ linux-next-20211224/tools/perf/pmu-events/arch/x86/broadwell/uncore.j= son > @@ -184,8 +184,8 @@ > "EventCode": "0x80", > "UMask": "0x01", > "EventName": "UNC_ARB_TRK_OCCUPANCY.ALL", > - "BriefDescription": "Each cycle count number of all Core outgoing va= lid entries. Such entry is defined as valid from it's allocation till first= of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-cohere= nt traffic.", > - "PublicDescription": "Each cycle count number of all Core outgoing v= alid entries. Such entry is defined as valid from it's allocation till firs= t of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-coher= ent traffic.", > + "BriefDescription": "Each cycle count number of all Core outgoing va= lid entries. Such entry is defined as valid from its allocation till first = of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-coheren= t traffic.", > + "PublicDescription": "Each cycle count number of all Core outgoing v= alid entries. Such entry is defined as valid from its allocation till first= of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-cohere= nt traffic.", > "Counter": "0,", > "CounterMask": "0", > "Invert": "0", > @@ -275,4 +275,4 @@ > "Invert": "0", > "EdgeDetect": "0" > } > -] > \ No newline at end of file > +] > --- linux-next-20211224.orig/tools/perf/pmu-events/arch/x86/cascadelakex/= uncore-other.json > +++ linux-next-20211224/tools/perf/pmu-events/arch/x86/cascadelakex/uncor= e-other.json > @@ -514,7 +514,7 @@ > "EventCode": "0x5C", > "EventName": "UNC_CHA_SNOOP_RESP.RSP_FWD_WB", > "PerPkg": "1", > - "PublicDescription": "Counts when a transaction with the opcode = type Rsp*Fwd*WB Snoop Response was received which indicates the data was wr= itten back to it's home socket, and the cacheline was forwarded to the requ= estor socket. This snoop response is only used in >=3D 4 socket systems. = It is used when a snoop HITM's in a remote caching agent and it directly fo= rwards data to a requestor, and simultaneously returns data to it's home so= cket to be written back to memory.", > + "PublicDescription": "Counts when a transaction with the opcode = type Rsp*Fwd*WB Snoop Response was received which indicates the data was wr= itten back to its home socket, and the cacheline was forwarded to the reque= stor socket. This snoop response is only used in >=3D 4 socket systems. I= t is used when a snoop HITM's in a remote caching agent and it directly for= wards data to a requestor, and simultaneously returns data to its home sock= et to be written back to memory.", > "UMask": "0x20", > "Unit": "CHA" > }, > @@ -524,7 +524,7 @@ > "EventCode": "0x5C", > "EventName": "UNC_CHA_SNOOP_RESP.RSP_WBWB", > "PerPkg": "1", > - "PublicDescription": "Counts when a transaction with the opcode = type Rsp*WB Snoop Response was received which indicates which indicates the= data was written back to it's home. This is returned when a non-RFO reque= st hits a cacheline in the Modified state. The Cache can either downgrade t= he cacheline to a S (Shared) or I (Invalid) state depending on how the syst= em has been configured. This reponse will also be sent when a cache reques= ts E (Exclusive) ownership of a cache line without receiving data, because = the cache must acquire ownership.", > + "PublicDescription": "Counts when a transaction with the opcode = type Rsp*WB Snoop Response was received which indicates which indicates the= data was written back to its home. This is returned when a non-RFO reques= t hits a cacheline in the Modified state. The Cache can either downgrade th= e cacheline to a S (Shared) or I (Invalid) state depending on how the syste= m has been configured. This response will also be sent when a cache reques= ts E (Exclusive) ownership of a cache line without receiving data, because = the cache must acquire ownership.", > "UMask": "0x10", > "Unit": "CHA" > }, > --- linux-next-20211224.orig/tools/perf/pmu-events/arch/x86/haswell/uncor= e.json > +++ linux-next-20211224/tools/perf/pmu-events/arch/x86/haswell/uncore.jso= n > @@ -304,8 +304,8 @@ > "EventCode": "0x80", > "UMask": "0x01", > "EventName": "UNC_ARB_TRK_OCCUPANCY.ALL", > - "BriefDescription": "Each cycle count number of all Core outgoing va= lid entries. Such entry is defined as valid from it's allocation till first= of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-cohere= nt traffic.", > - "PublicDescription": "Each cycle count number of all Core outgoing v= alid entries. Such entry is defined as valid from it's allocation till firs= t of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-coher= ent traffic.", > + "BriefDescription": "Each cycle count number of all Core outgoing va= lid entries. Such entry is defined as valid from its allocation till first = of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-coheren= t traffic.", > + "PublicDescription": "Each cycle count number of all Core outgoing v= alid entries. Such entry is defined as valid from its allocation till first= of IDI0 or DRS0 messages is sent out. Accounts for Coherent and non-cohere= nt traffic.", > "Counter": "0", > "CounterMask": "0", > "Invert": "0", > @@ -371,4 +371,4 @@ > "Invert": "0", > "EdgeDetect": "0" > } > -] > \ No newline at end of file > +] > --- linux-next-20211224.orig/tools/perf/pmu-events/arch/x86/skylakex/unco= re-other.json > +++ linux-next-20211224/tools/perf/pmu-events/arch/x86/skylakex/uncore-ot= her.json > @@ -514,7 +514,7 @@ > "EventCode": "0x5C", > "EventName": "UNC_CHA_SNOOP_RESP.RSP_FWD_WB", > "PerPkg": "1", > - "PublicDescription": "Counts when a transaction with the opcode = type Rsp*Fwd*WB Snoop Response was received which indicates the data was wr= itten back to it's home socket, and the cacheline was forwarded to the requ= estor socket. This snoop response is only used in >=3D 4 socket systems. = It is used when a snoop HITM's in a remote caching agent and it directly fo= rwards data to a requestor, and simultaneously returns data to it's home so= cket to be written back to memory.", > + "PublicDescription": "Counts when a transaction with the opcode = type Rsp*Fwd*WB Snoop Response was received which indicates the data was wr= itten back to its home socket, and the cacheline was forwarded to the reque= stor socket. This snoop response is only used in >=3D 4 socket systems. I= t is used when a snoop HITM's in a remote caching agent and it directly for= wards data to a requestor, and simultaneously returns data to its home sock= et to be written back to memory.", > "UMask": "0x20", > "Unit": "CHA" > }, > @@ -524,7 +524,7 @@ > "EventCode": "0x5C", > "EventName": "UNC_CHA_SNOOP_RESP.RSP_WBWB", > "PerPkg": "1", > - "PublicDescription": "Counts when a transaction with the opcode = type Rsp*WB Snoop Response was received which indicates which indicates the= data was written back to it's home. This is returned when a non-RFO reque= st hits a cacheline in the Modified state. The Cache can either downgrade t= he cacheline to a S (Shared) or I (Invalid) state depending on how the syst= em has been configured. This reponse will also be sent when a cache reques= ts E (Exclusive) ownership of a cache line without receiving data, because = the cache must acquire ownership.", > + "PublicDescription": "Counts when a transaction with the opcode = type Rsp*WB Snoop Response was received which indicates which indicates the= data was written back to its home. This is returned when a non-RFO reques= t hits a cacheline in the Modified state. The Cache can either downgrade th= e cacheline to a S (Shared) or I (Invalid) state depending on how the syste= m has been configured. This response will also be sent when a cache reques= ts E (Exclusive) ownership of a cache line without receiving data, because = the cache must acquire ownership.", > "UMask": "0x10", > "Unit": "CHA" > },