Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1187725pxf; Fri, 9 Apr 2021 02:09:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwmmNncySji4QhAYBL+EvndZHF/45TY98cT5vTEENnzUAGb79qZ1U7mAaH0bEU1G+kqafWM X-Received: by 2002:a17:90b:a18:: with SMTP id gg24mr12840050pjb.161.1617959394358; Fri, 09 Apr 2021 02:09:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617959394; cv=none; d=google.com; s=arc-20160816; b=RYQwPBARU+YE7jEexTwso1URo5TI/K8ErJlB0qf4DVAgrmOrvmYxBSDgvWsgJGc3mc KukqkiUZEkZgICsWZC0jjq4NY+l1+v+ouwB94gwgnGYsU7n1gfawDIZ5R62O6JZl4f/X 0M4nZO92VA9PJwtGqXIjNgLruyPeVObvmGF1FV1e00IHLWmxrKSyhhJ3U8bvUDMvhZAD z8W9T0tzN+jAxNVF82hoBJdFkS3lYzJMAgv+rC8Jo6uQoxke+K66aOFaZLwvJWHNO0U3 mACKp+Xm8knrVSjXtljdgX4yIFh1Oeq8iiegTDTVDEl5OaECYfZmiqOgz4csw9nuKo5X PtyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=XKLJVk2IjVQ96MjvwDB3gO3yBVGOpP0VI9IBl8YaAn4=; b=QQvAPvWnpOJDNnSMUVul125Gjj5bjaD7DkFj+RRNzZ7ebL/F/FbxkzHF2q4QoX3LQ5 yGlz/1a6Aa8uXGRs1RO8nGWmdqCVJNVN5DIy1QTcPFgWDRylcyIQTJW06ufrKV+rG0ue GSKSOllafP/Yam5BGBkyipM3g+wYqJ4WAC7EX2BTcbVXMyOGWS3ACIpzUI/t6/KfTWFO G48b0Y8pI7C5zv2U4gxV6nSCMZG+9192TCoFIx7/aH9Jxqg9xabxl5XVUqBWACt/szCp sq0ooHu/MtGPDdPzKymm4/k6O7koFSkUKKNbAn4vPGMapo0K247mOC0Jb3JERFEIfH9q FQqw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e3si2124139plj.4.2021.04.09.02.09.42; Fri, 09 Apr 2021 02:09:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233284AbhDIJJC (ORCPT + 99 others); Fri, 9 Apr 2021 05:09:02 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:16502 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232276AbhDIJI5 (ORCPT ); Fri, 9 Apr 2021 05:08:57 -0400 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4FGsg719SdzPnx8; Fri, 9 Apr 2021 17:05:55 +0800 (CST) Received: from localhost.localdomain (10.67.165.24) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.498.0; Fri, 9 Apr 2021 17:08:33 +0800 From: Qi Liu To: , , CC: , , , , Subject: [PATCH v2 2/2] docs: perf: Add description for HiSilicon PCIe PMU driver Date: Fri, 9 Apr 2021 17:05:57 +0800 Message-ID: <1617959157-22956-3-git-send-email-liuqi115@huawei.com> X-Mailer: git-send-email 2.8.1 In-Reply-To: <1617959157-22956-1-git-send-email-liuqi115@huawei.com> References: <1617959157-22956-1-git-send-email-liuqi115@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.67.165.24] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org PCIe PMU Root Complex Integrated End Point(RCiEP) device is supported on HiSilicon HIP09 platform. Document it to provide guidance on how to use it. Signed-off-by: Qi Liu --- Documentation/admin-guide/perf/hisi-pcie-pmu.rst | 104 +++++++++++++++++++++++ 1 file changed, 104 insertions(+) create mode 100644 Documentation/admin-guide/perf/hisi-pcie-pmu.rst diff --git a/Documentation/admin-guide/perf/hisi-pcie-pmu.rst b/Documentation/admin-guide/perf/hisi-pcie-pmu.rst new file mode 100644 index 0000000..2084b53 --- /dev/null +++ b/Documentation/admin-guide/perf/hisi-pcie-pmu.rst @@ -0,0 +1,104 @@ +================================================ +HiSilicon PCIe Performance Monitoring Unit (PMU) +================================================ + +HiSilicon PCIe Performance Monitoring Unit (PMU) is a PCIe Root Complex +integrated End Point (RCiEP) device. On Hip09, each PCIe Core has a PMU RCiEP +to monitor multi Root Ports and all Endpoints downstream these Root Ports. + +HiSilicon PCIe PMU is supported to collect performance data of PCIe bus, such +as: bandwidth, latency etc. + + +HiSilicon PCIe PMU driver +========================= + +The PCIe PMU driver registers a perf PMU with the name of its sicl-id and PCIe +Core id.:: + + /sys/bus/event_source/hisi_pcie_ + +PMU driver provides description of available events and filter options in sysfs, +see /sys/bus/event_source/devices/hisi_pcie_. + +The "format" directory describes all formats of the config (events) and config1 +(filter options) fields of the perf_event_attr structure. The "events" directory +describes all documented events shown in perf list. + +The "identifier" sysfs file allows users to identify the version of the +PMU hardware device. + +The "bus" sysfs file allows users to get the bus number of Root Ports +monitored by PMU. + +Example usage of perf:: + + $# perf list + hisi_pcie0_0/bw_rx/ [kernel PMU event] + ------------------------------------------ + + $# perf stat -e hisi_pcie0_0/bw_rx/ sleep 5 + +The current driver does not support sampling. So "perf record" is unsupported. +Also attach to a task is unsupported for PCIe PMU. + +Filter options +-------------- + +1. Target filter +PMU could only monitor the performance of traffic downstream target Root Ports +or downstream target Endpoint. PCIe PMU driver support "port" and "bdf" +interfaces for users, and these two interfaces aren't supported at the same +time. + +-port +"port" filter can be used in all PCIe PMU events, target Root Port can be +selected by configuring the 16-bits-bitmap "port". Multi ports can be selected +for AP-layer-events, and only one port can be selected for TL/DL-layer-events. + +For example, if target Root Port is 0000:00:00.0 (x8 lanes), bit0 of bitmap +should be set, port=0x1; if target Root Port is 0000:00:04.0 (x4 lanes), +bit8 is set, port=0x100; if these two Root Ports are both monitored, port=0x101. + +Example usage of perf:: + + $# perf stat -e hisi_pcie0_0/bw_rx,port=0x1/ sleep 5 + +-bdf + +"bdf" filter can only be used in bandwidth events, target Endpoint is selected +by configuring BDF to "bdf". Counter only counts the bandwidth of message +requested by target Endpoint. + +For example, "bdf=0x3900" means BDF of target Endpoint is 0000:39:00.0. + +Example usage of perf:: + + $# perf stat -e hisi_pcie0_0/bw_rx,bdf=0x3900/ sleep 5 + +2. Trigger filter +Event statistics start when the first time TLP length is greater/smaller +than trigger condition. You can set the trigger condition by writing "trig_len", +and set the trigger mode by writing "trig_mode". This filter can only be used +in bandwidth events. + +For example, "trig_len=4" means trigger condition is 2^4 DW, "trig_mode=0" +means statistics start when TLP length > trigger condition, "trig_mode=1" +means start when TLP length < condition. + +Example usage of perf:: + + $# perf stat -e hisi_pcie0_0/bw_rx,trig_len=0x4,trig_mode=1/ sleep 5 + +3. Threshold filter +Counter counts when TLP length within the specified range. You can set the +threshold by writing "thr_len", and set the threshold mode by writing +"thr_mode". This filter can only be used in bandwidth events. + +For example, "thr_len=4" means threshold is 2^4 DW, "thr_mode=0" means +counter counts when TLP length >= threshold, and "thr_mode=1" means counts +when TLP length < threshold. + +Example usage of perf:: + + $# perf stat -e hisi_pcie0_0/bw_rx,thr_len=0x4,thr_mode=1/ sleep 5 -- 2.8.1