public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: wangyushan <wangyushan12@huawei.com>
To: <will@kernel.org>, <mark.rutland@arm.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Cc: <robin.murphy@arm.com>, <yangyicong@huawei.com>,
	<Jonathan.Cameron@huawei.com>, <liuyonglong@huawei.com>,
	<wanghuiqiang@huawei.com>, <prime.zeng@hisilicon.com>,
	<hejunhao3@h-partners.com>, <fanghao11@huawei.com>,
	Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH v3 0/9] Updates of HiSilicon Uncore L3C PMU
Date: Thu, 11 Sep 2025 21:22:27 +0800	[thread overview]
Message-ID: <54fb6d7e-3c42-4dff-9bc7-b98cba75e3e1@huawei.com> (raw)
In-Reply-To: <20250829101427.2557899-1-wangyushan12@huawei.com>

A gentle ping...

On 8/29/2025 6:14 PM, Yushan Wang wrote:
> Support new version of L3C PMU, which supports extended events space
> which can be controlled in up to 2 extra address spaces with separate
> overflow interrupts.  The layout of the control/event registers are kept
> the same.  The extended events with original ones together cover the
> monitoring job of all transactions on L3C.
>
> That's said, the driver supports finer granual statistics of L3 cache
> with separated and dedicated PMUs, and a new option `ext` to give a
> hint of to which part should perf counting command be delivered.
>
> The extended events is specified with `ext=[1|2]` option for the driver
> to distinguish:
>
> perf stat -e hisi_sccl0_l3c0_0/event=<event_id>,ext=<ext>/
>
> Currently only event option using config bit [7, 0]. There's still
> plenty unused space. Make ext using config [16, 17] and reserve
> bit [15, 8] for event option for future extension.
>
> With the capability of extra counters, number of counters for HiSilicon
> uncore PMU could reach up to 24, the usedmap is extended accordingly.
>
> The hw_perf_event::event_base is initialized to the base MMIO address
> of the event and will be used for later control, overflow handling and
> counts readout.
>
> We still make use of the Uncore PMU framework for handling the events
> and interrupt migration on CPU hotplug. The framework's cpuhp callback
> will handle the event migration and interrupt migration of orginial
> event, if PMU supports extended events then the interrupt of extended
> events is migrated to the same CPU choosed by the framework.
>
> A new HID of HISI0215 is used for this version of L3C PMU.
>
> Some necessary refactor is included, allowing the framework to cope with
> the new version of driver.
>
> Depends-on: drivers/perf: hisi: Add support for HiSilicon NOC and MN PMU driver
> Depends-on: Message-ID: <20250717121727.61057-1-yangyicong@huawei.com>
>
> ---
>
> Changes:
>
> v2 -> v3:
>    - Refactor made for better readability.
>    - Fixed failure examination in cpu offline callback.
>    - Some minor reword of documentation, and droped subsection titles as
>      suggested by Yicong.
>    - Link to v2: https://lore.kernel.org/all/20250821135049.2010220-1-wangyushan12@huawei.com/
>
> v1 -> v2:
>    - Don't call disable_irq() and simply return success when there is no
>      CPU available for irq migration.
>    - Documentation patch split.
>    - Fix of a few other issues etc. per Jonathan.
>    - Link to v1: https://lore.kernel.org/all/20250729153823.2026154-1-wangyushan12@huawei.com/
>
> Yicong Yang (7):
>    drivers/perf: hisi: Relax the event ID check in the framework
>    drivers/perf: hisi: Export hisi_uncore_pmu_isr()
>    drivers/perf: hisi: Simplify the probe process of each L3C PMU version
>    drivers/perf: hisi: Extract the event filter check of L3C PMU
>    drivers/perf: hisi: Extend the field of tt_core
>    drivers/perf: hisi: Refactor the event configuration of L3C PMU
>    drivers/perf: hisi: Add support for L3C PMU v3
>
> Yushan Wang (2):
>    Documentation: hisi-pmu: Fix of minor format error
>    Documentation: hisi-pmu: Add introduction to HiSilicon V3 PMU
>
>   Documentation/admin-guide/perf/hisi-pmu.rst  |  38 +-
>   drivers/perf/hisilicon/hisi_uncore_l3c_pmu.c | 528 +++++++++++++++----
>   drivers/perf/hisilicon/hisi_uncore_pmu.c     |   5 +-
>   drivers/perf/hisilicon/hisi_uncore_pmu.h     |   6 +-
>   4 files changed, 481 insertions(+), 96 deletions(-)
>



  parent reply	other threads:[~2025-09-11 13:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 10:14 [PATCH v3 0/9] Updates of HiSilicon Uncore L3C PMU Yushan Wang
2025-08-29 10:14 ` [PATCH v3 1/9] drivers/perf: hisi: Relax the event ID check in the framework Yushan Wang
2025-08-29 10:14 ` [PATCH v3 2/9] drivers/perf: hisi: Export hisi_uncore_pmu_isr() Yushan Wang
2025-08-29 10:14 ` [PATCH v3 3/9] drivers/perf: hisi: Simplify the probe process of each L3C PMU version Yushan Wang
2025-08-29 10:14 ` [PATCH v3 4/9] drivers/perf: hisi: Extract the event filter check of L3C PMU Yushan Wang
2025-08-29 10:14 ` [PATCH v3 5/9] drivers/perf: hisi: Extend the field of tt_core Yushan Wang
2025-09-22 13:17   ` Will Deacon
2025-09-23  7:31     ` Yicong Yang
2025-09-24 11:19       ` Will Deacon
2025-09-25  3:59         ` Yicong Yang
2025-08-29 10:14 ` [PATCH v3 6/9] drivers/perf: hisi: Refactor the event configuration of L3C PMU Yushan Wang
2025-08-29 10:14 ` [PATCH v3 7/9] drivers/perf: hisi: Add support for L3C PMU v3 Yushan Wang
2025-08-29 10:14 ` [PATCH v3 8/9] Documentation: hisi-pmu: Fix of minor format error Yushan Wang
2025-08-29 10:14 ` [PATCH v3 9/9] Documentation: hisi-pmu: Add introduction to HiSilicon V3 PMU Yushan Wang
2025-09-01  6:49   ` Yicong Yang
2025-09-11 13:22 ` wangyushan [this message]
2025-09-22 13:14 ` [PATCH v3 0/9] Updates of HiSilicon Uncore L3C PMU 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=54fb6d7e-3c42-4dff-9bc7-b98cba75e3e1@huawei.com \
    --to=wangyushan12@huawei.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=fanghao11@huawei.com \
    --cc=hejunhao3@h-partners.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=robin.murphy@arm.com \
    --cc=wanghuiqiang@huawei.com \
    --cc=will@kernel.org \
    --cc=yangyicong@huawei.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