From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: dwc_pcie_pmu: Fix the mnemonics and eventid
Date: Thu, 5 Dec 2024 15:26:14 +0800 [thread overview]
Message-ID: <ac669a87-7517-4a37-8026-67b70e99884c@linux.alibaba.com> (raw)
In-Reply-To: <20241205061914.5568-3-ilkka@os.amperecomputing.com>
在 2024/12/5 14:19, Ilkka Koskinen 写道:
> Fix the event id and type in the example. In addition, the recent fix,
> which addressed the mnemonics with mixed case, didn't fix the document.
> Match the names with the driver.
>
> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
> ---
> Documentation/admin-guide/perf/dwc_pcie_pmu.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/admin-guide/perf/dwc_pcie_pmu.rst b/Documentation/admin-guide/perf/dwc_pcie_pmu.rst
> index 39b8e1fdd0cd..cb376f335f40 100644
> --- a/Documentation/admin-guide/perf/dwc_pcie_pmu.rst
> +++ b/Documentation/admin-guide/perf/dwc_pcie_pmu.rst
> @@ -60,7 +60,7 @@ description of available events and configuration options in sysfs, see
> The "format" directory describes format of the config fields of the
> perf_event_attr structure. The "events" directory provides configuration
> templates for all documented events. For example,
> -"Rx_PCIe_TLP_Data_Payload" is an equivalent of "eventid=0x22,type=0x1".
> +"rx_pcie_tlp_data_payload" is an equivalent of "eventid=0x21,type=0x0".
>
> The "perf list" command shall list the available events from sysfs, e.g.::
>
> @@ -79,8 +79,8 @@ Example usage of counting PCIe RX TLP data payload (Units of bytes)::
>
> The average RX/TX bandwidth can be calculated using the following formula:
>
> - PCIe RX Bandwidth = Rx_PCIe_TLP_Data_Payload / Measure_Time_Window
> - PCIe TX Bandwidth = Tx_PCIe_TLP_Data_Payload / Measure_Time_Window
> + PCIe RX Bandwidth = rx_pcie_tlp_data_payload / Measure_Time_Window
> + PCIe TX Bandwidth = tx_pcie_tlp_data_payload / Measure_Time_Window
>
> Lane Event Usage
> -------------------------------
LGTM.
Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>
Thanks.
Best Regards,
Shuai
next prev parent reply other threads:[~2024-12-05 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 6:19 [PATCH 0/2] perf/dwc_pcie: Fix the swapped event numbers as well as the documentation Ilkka Koskinen
2024-12-05 6:19 ` [PATCH 1/2] perf/dwc_pcie: Fix the event numbers Ilkka Koskinen
2024-12-05 7:25 ` Shuai Xue
2024-12-05 6:19 ` [PATCH 2/2] Documentation: dwc_pcie_pmu: Fix the mnemonics and eventid Ilkka Koskinen
2024-12-05 7:26 ` Shuai Xue [this message]
2024-12-05 7:24 ` [PATCH 0/2] perf/dwc_pcie: Fix the swapped event numbers as well as the documentation Shuai Xue
2024-12-09 18:43 ` 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=ac669a87-7517-4a37-8026-67b70e99884c@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=ilkka@os.amperecomputing.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.com \
--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®