public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Yushan Wang <wangyushan12@huawei.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	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, linuxarm@huawei.com,
	fanghao11@huawei.com
Subject: Re: [PATCH v3 0/9] Updates of HiSilicon Uncore L3C PMU
Date: Mon, 22 Sep 2025 14:14:51 +0100	[thread overview]
Message-ID: <175854328084.3142502.15045454616796206368.b4-ty@kernel.org> (raw)
In-Reply-To: <20250829101427.2557899-1-wangyushan12@huawei.com>

On Fri, 29 Aug 2025 18:14:18 +0800, 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.
> 
> [...]

Applied to will (for-next/perf), thanks!

But please see my comment on patch 5 regarding the user ABI.

[1/9] drivers/perf: hisi: Relax the event ID check in the framework
      https://git.kernel.org/will/c/43de0ac332b8
[2/9] drivers/perf: hisi: Export hisi_uncore_pmu_isr()
      https://git.kernel.org/will/c/4550244b53b7
[3/9] drivers/perf: hisi: Simplify the probe process of each L3C PMU version
      https://git.kernel.org/will/c/0960e535be54
[4/9] drivers/perf: hisi: Extract the event filter check of L3C PMU
      https://git.kernel.org/will/c/2271f1634243
[5/9] drivers/perf: hisi: Extend the field of tt_core
      https://git.kernel.org/will/c/ede339ff61c6
[6/9] drivers/perf: hisi: Refactor the event configuration of L3C PMU
      https://git.kernel.org/will/c/b3abb08d6f62
[7/9] drivers/perf: hisi: Add support for L3C PMU v3
      https://git.kernel.org/will/c/475d94dfe7c6
[8/9] Documentation: hisi-pmu: Fix of minor format error
      https://git.kernel.org/will/c/272dd0e5e58d
[9/9] Documentation: hisi-pmu: Add introduction to HiSilicon V3 PMU
      https://git.kernel.org/will/c/6d2f913fda56

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      parent reply	other threads:[~2025-09-22 13:15 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 ` [PATCH v3 0/9] Updates of HiSilicon Uncore L3C PMU wangyushan
2025-09-22 13:14 ` Will Deacon [this message]

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=175854328084.3142502.15045454616796206368.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=fanghao11@huawei.com \
    --cc=hejunhao3@h-partners.com \
    --cc=kernel-team@android.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=wangyushan12@huawei.com \
    --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