Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Yicong Yang <yangyicong@huawei.com>
To: Shaokun Zhang <zhangshaokun@hisilicon.com>, <liuqi6124@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	<jonathan.cameron@huawei.com>, <bagasdotme@gmail.com>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-doc@vger.kernel.org>, <linux-pci@vger.kernel.org>,
	<linuxarm@huawei.com>, <f.fangjian@huawei.com>,
	<prime.zeng@huawei.com>, <shenyang39@huawei.com>
Subject: [PATCH v3 1/4] drivers/perf: hisi: Fix some event id for hisi-pcie-pmu
Date: Thu, 17 Nov 2022 16:41:33 +0800	[thread overview]
Message-ID: <20221117084136.53572-2-yangyicong@huawei.com> (raw)
In-Reply-To: <20221117084136.53572-1-yangyicong@huawei.com>

From: Yicong Yang <yangyicong@hisilicon.com>

Some event id of hisi-pcie-pmu is incorrect, fix them.

Fixes: 8404b0fbc7fb ("drivers/perf: hisi: Add driver for HiSilicon PCIe PMU")
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
---
 drivers/perf/hisilicon/hisi_pcie_pmu.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/perf/hisilicon/hisi_pcie_pmu.c b/drivers/perf/hisilicon/hisi_pcie_pmu.c
index 21771708597d..071e63d9a9ac 100644
--- a/drivers/perf/hisilicon/hisi_pcie_pmu.c
+++ b/drivers/perf/hisilicon/hisi_pcie_pmu.c
@@ -693,10 +693,10 @@ static struct attribute *hisi_pcie_pmu_events_attr[] = {
 	HISI_PCIE_PMU_EVENT_ATTR(rx_mrd_cnt, 0x10210),
 	HISI_PCIE_PMU_EVENT_ATTR(tx_mrd_latency, 0x0011),
 	HISI_PCIE_PMU_EVENT_ATTR(tx_mrd_cnt, 0x10011),
-	HISI_PCIE_PMU_EVENT_ATTR(rx_mrd_flux, 0x1005),
-	HISI_PCIE_PMU_EVENT_ATTR(rx_mrd_time, 0x11005),
-	HISI_PCIE_PMU_EVENT_ATTR(tx_mrd_flux, 0x2004),
-	HISI_PCIE_PMU_EVENT_ATTR(tx_mrd_time, 0x12004),
+	HISI_PCIE_PMU_EVENT_ATTR(rx_mrd_flux, 0x0804),
+	HISI_PCIE_PMU_EVENT_ATTR(rx_mrd_time, 0x10804),
+	HISI_PCIE_PMU_EVENT_ATTR(tx_mrd_flux, 0x0405),
+	HISI_PCIE_PMU_EVENT_ATTR(tx_mrd_time, 0x10405),
 	NULL
 };
 
-- 
2.24.0


  reply	other threads:[~2022-11-17  8:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17  8:41 [PATCH v3 0/4] Add TLP filter support and some fixes for HiSilicon PCIe PMU Yicong Yang
2022-11-17  8:41 ` Yicong Yang [this message]
2022-11-17  8:41 ` [PATCH v3 2/4] docs: perf: Fix PMU instance name of hisi-pcie-pmu Yicong Yang
2022-11-17  8:41 ` [PATCH v3 3/4] Documentation: perf: Indent filter options list " Yicong Yang
2022-11-17  8:41 ` [PATCH v3 4/4] drivers/perf: hisi: Add TLP filter support Yicong Yang
2022-11-29 11:10 ` [PATCH v3 0/4] Add TLP filter support and some fixes for HiSilicon PCIe PMU Yicong Yang
2022-11-29 19:52 ` 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=20221117084136.53572-2-yangyicong@huawei.com \
    --to=yangyicong@huawei.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=f.fangjian@huawei.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=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuqi6124@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=prime.zeng@huawei.com \
    --cc=shenyang39@huawei.com \
    --cc=will@kernel.org \
    --cc=zhangshaokun@hisilicon.com \
    /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