From: Yicong Yang <yangyicong@huawei.com>
To: <will@kernel.org>, <mark.rutland@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <hejunhao3@huawei.com>, <jonathan.cameron@huawei.com>,
<prime.zeng@hisilicon.com>, <linuxarm@huawei.com>,
<yangyicong@hisilicon.com>, <wangyushan12@huawei.com>
Subject: [PATCH v4 0/2] drivers/perf: hisi: Add support for HiSilicon MN PMU driver
Date: Thu, 17 Jul 2025 15:41:36 +0800 [thread overview]
Message-ID: <20250717074138.39903-1-yangyicong@huawei.com> (raw)
From: Yicong Yang <yangyicong@hisilicon.com>
Add support for two new Uncore PMUs to monitor the events of the system bus
(by NoC PMU) and the DVM operations (by MN PMU).
Change since v3:
- Use ACPI driver data to retrieve the hardware capabilities
Link: https://lore.kernel.org/linux-arm-kernel/20250619125557.57372-1-yangyicong@huawei.com/
Junhao He (1):
drivers/perf: hisi: Add support for HiSilicon MN PMU driver
Yicong Yang (1):
drivers/perf: hisi: Add support for HiSilicon NoC PMU
Documentation/admin-guide/perf/hisi-pmu.rst | 11 +
drivers/perf/hisilicon/Makefile | 3 +-
drivers/perf/hisilicon/hisi_uncore_mn_pmu.c | 411 +++++++++++++++++
drivers/perf/hisilicon/hisi_uncore_noc_pmu.c | 443 +++++++++++++++++++
4 files changed, 867 insertions(+), 1 deletion(-)
create mode 100644 drivers/perf/hisilicon/hisi_uncore_mn_pmu.c
create mode 100644 drivers/perf/hisilicon/hisi_uncore_noc_pmu.c
--
2.24.0
next reply other threads:[~2025-07-17 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 7:41 Yicong Yang [this message]
2025-07-17 7:41 ` [PATCH v4 1/2] drivers/perf: hisi: Add support for HiSilicon NoC PMU Yicong Yang
2025-07-17 10:37 ` Jonathan Cameron
2025-07-17 7:41 ` [PATCH v4 2/2] drivers/perf: hisi: Add support for HiSilicon MN PMU driver Yicong Yang
2025-07-17 10:39 ` Jonathan Cameron
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=20250717074138.39903-1-yangyicong@huawei.com \
--to=yangyicong@huawei.com \
--cc=hejunhao3@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=wangyushan12@huawei.com \
--cc=will@kernel.org \
--cc=yangyicong@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
all inboxes | Powered by JetHome®