From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 867B6CDB465 for ; Thu, 19 Oct 2023 11:07:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:CC:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=YFrIbqjxCIFrLTDz3s3eCMpkMjVFHb0LMEzc223D28Q=; b=em8yfzUGU10aWQ quIwA3zgCUTpU+5gTeTqVZxUA0kY4kruHrLKjGDBdSDZ493DG4DsXnmvCT2M8l4Ozp8im9cpKovJ8 byMJCnZ+5pYgvv987KmCD5TXz7I+7L0WGhyHZdNuAoIeh10mpXQCu6JMVInZ1v7XAGLPSZcSjuQwk eA5zbAy4m/E1WI3bLI2VG0hfMpdrHbvtXasj6TEf7h42oJuSmJpHCav8grRySR8zIYU+fPmdF47vx DJml6xCfo+KxitrBHOEAqsTdhmq4h/YCbuBaP+lfAgqFFZ8IqyYjgXXj7d5fMieaXoc2xB2b2bR9c W2hYw4mHeRHc6/VzdXJw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qtQrp-00H7pS-19; Thu, 19 Oct 2023 11:07:05 +0000 Received: from frasgout.his.huawei.com ([185.176.79.56]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qtQrl-00H7nz-2a for linux-arm-kernel@lists.infradead.org; Thu, 19 Oct 2023 11:07:04 +0000 Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SB4Zh3HjVz6HJLt; Thu, 19 Oct 2023 19:03:24 +0800 (CST) Received: from localhost (10.202.227.76) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Thu, 19 Oct 2023 12:06:48 +0100 Date: Thu, 19 Oct 2023 12:06:47 +0100 From: Jonathan Cameron To: Shuai Xue CC: , , , , , , , , , , , , , Subject: Re: [PATCH v8 1/4] docs: perf: Add description for Synopsys DesignWare PCIe PMU driver Message-ID: <20231019120647.00007589@Huawei.com> In-Reply-To: References: <20231017013235.27831-1-xueshuai@linux.alibaba.com> <20231017013235.27831-2-xueshuai@linux.alibaba.com> <20231017101624.00003231@Huawei.com> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) MIME-Version: 1.0 X-Originating-IP: [10.202.227.76] X-ClientProxiedBy: lhrpeml100002.china.huawei.com (7.191.160.241) To lhrpeml500005.china.huawei.com (7.191.163.240) X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231019_040702_215451_FD2292CE X-CRM114-Status: GOOD ( 39.49 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 18 Oct 2023 09:19:51 +0800 Shuai Xue wrote: > On 2023/10/17 17:16, Jonathan Cameron wrote: > > On Tue, 17 Oct 2023 09:32:32 +0800 > > Shuai Xue wrote: > > > >> Alibaba's T-Head Yitan 710 SoC includes Synopsys' DesignWare Core PCIe > >> controller which implements which implements PMU for performance and > >> functional debugging to facilitate system maintenance. > >> > >> Document it to provide guidance on how to use it. > >> > >> Signed-off-by: Shuai Xue > >> Reviewed-by: Baolin Wang > > > > A few minor things inline and one question that I'd like a comment on > > for my understanding at least! (why not multiply the counter by 16 and > > make the maths simpler?) > > > > With those tidied up, > > Reviewed-by: Jonathan Cameron > > > > Thank you for providing prompt feedback and valuable comments to me. > (please also see my replies inline) > > Best Regards, > Shuai > > > > > > >> --- > >> .../admin-guide/perf/dwc_pcie_pmu.rst | 94 +++++++++++++++++++ > >> Documentation/admin-guide/perf/index.rst | 1 + > >> 2 files changed, 95 insertions(+) > >> create mode 100644 Documentation/admin-guide/perf/dwc_pcie_pmu.rst > >> > >> diff --git a/Documentation/admin-guide/perf/dwc_pcie_pmu.rst b/Documentation/admin-guide/perf/dwc_pcie_pmu.rst > >> new file mode 100644 > >> index 000000000000..eac1b6f36450 > >> --- /dev/null > >> +++ b/Documentation/admin-guide/perf/dwc_pcie_pmu.rst > >> @@ -0,0 +1,94 @@ > >> +====================================================================== > >> +Synopsys DesignWare Cores (DWC) PCIe Performance Monitoring Unit (PMU) > >> +====================================================================== > >> + > >> +DesignWare Cores (DWC) PCIe PMU > >> +=============================== > >> + > >> +The PMU is a PCIe configuration space register block provided by each PCIe Root > >> +Port in a Vendor-Specific Extended Capability named RAS D.E.S (Debug, Error > >> +injection, and Statistics). > >> + > >> +As the name indicates, the RAS DES capability supports system level > >> +debugging, AER error injection, and collection of statistics. To facilitate > >> +collection of statistics, Synopsys DesignWare Cores PCIe controller > >> +provides the following two features: > >> + > >> +- one 64-bit counter for Time Based Analysis (RX/TX data throughput and > >> + time spent in each low-power LTSSM state) and > >> +- one 32-bit counter for Event Counting (error and non-error events for > >> + a specified lane) > >> + > >> +Note: There is no interrupt for counter overflow. > >> + > >> +Time Based Analysis > >> +------------------- > >> + > >> +Using this feature you can obtain information regarding RX/TX data > >> +throughput and time spent in each low-power LTSSM state by the controller. > >> +The PMU measures data in two categories: > >> + > >> +- Group#0: Percentage of time the controller stays in LTSSM states. > >> +- Group#1: Amount of data processed (Units of 16 bytes). > >> + > >> +Lane Event counters > >> +------------------- > >> + > >> +Using this feature you can obtain Error and Non-Error information in > >> +specific lane by the controller. The PMU event is select by: > >> + > >> +- Group i > >> +- Event j within the Group i > >> +- and Lane k > > The and here is a little confusing. I'd rework as > > The PMU event is selected by all of: > > - Group i > > - Event j within the Group i > > - Lane k > > Will rework it in next version. > > > > >> + > >> +Some of the event only exist for specific configurations. > > > > events > > Sorry for typo, will fix it. > > > > >> + > >> +DesignWare Cores (DWC) PCIe PMU Driver > >> +======================================= > >> + > >> +This driver adds PMU devices for each PCIe Root Port named based on the BDF of > >> +the Root Port. For example, > >> + > >> + 30:03.0 PCI bridge: Device 1ded:8000 (rev 01) > >> + > >> +the PMU device name for this Root Port is dwc_rootport_3018. > >> + > >> +The DWC PCIe PMU driver registers a perf PMU driver, which provides > >> +description of available events and configuration options in sysfs, see > >> +/sys/bus/event_source/devices/dwc_rootport_{bdf}. > >> + > >> +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". > >> + > >> +The "perf list" command shall list the available events from sysfs, e.g.:: > >> + > >> + $# perf list | grep dwc_rootport > >> + <...> > >> + dwc_rootport_3018/Rx_PCIe_TLP_Data_Payload/ [Kernel PMU event] > >> + <...> > >> + dwc_rootport_3018/rx_memory_read,lane=?/ [Kernel PMU event] > >> + > >> +Time Based Analysis Event Usage > >> +------------------------------- > >> + > >> +Example usage of counting PCIe RX TLP data payload (Units of 16 bytes):: > >> + > >> + $# perf stat -a -e dwc_rootport_3018/Rx_PCIe_TLP_Data_Payload/ > >> + > >> +The average RX/TX bandwidth can be calculated using the following formula: > >> + > >> + PCIe RX Bandwidth = PCIE_RX_DATA * 16B / Measure_Time_Window > >> + PCIe TX Bandwidth = PCIE_TX_DATA * 16B / Measure_Time_Window > > > > Silly question (sorry I didn't raise it earlier) but can we make the interface > > more intuitive by just multiplying the counter value at point of read by 16? > > Really a good suggestion, and it is very convenient for end perf users. > But the unit of 16 is only applied to group#1 as described in Time Based Analysis > section. How hard would it be to just apply it to those events? Userspace doesn't care what the hardware does underneath - it just wants to get moderately intuitive data back. Having the end user deal with this oddity + even the need to document it seems to me to be unnecessary burden given how simple it is (I assume) to remove the oddity. > > So I prefer to left the unit part to end users. > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel