From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Myria Sarvay" <myrialsarvay@gmail.com>,
"Joshua Peisach" <jpeisach@ubuntu.com>
Cc: "Will Deacon" <will@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Sven Peter" <sven@kernel.org>, "Janne Grunau" <j@jannau.net>,
"Neal Gompa" <neal@gompa.dev>, "Marc Zyngier" <maz@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <asahi@lists.linux.dev>,
"Yuvan Shen" <yuvanshen09@gmail.com>,
"Nick Chan" <towinchenmi@gmail.com>
Subject: Re: [PATCH 00/13] drivers/perf: apple_m1: Add M3/M4/A18 Pro Support
Date: Mon, 16 Nov 2026 08:26:37 -0500 [thread overview]
Message-ID: <DMWO4APJSZPS.16AA1EABR1AEJ@ubuntu.com> (raw)
In-Reply-To: <CAFTKyQziVo3COsPZSSZOaFs7R6HhXEWNHYfgTkjyACc7bkoBDw@mail.gmail.com>
On Fri Nov 13, 2026 at 2:25 AM EST, Myria Sarvay wrote:
> On Sun, Nov 08, 2026 at 12:32:46PM -0500, Joshua Peisach wrote:
>> On Tue Nov 3, 2026 at 5:14 AM EST, Myria Sarvay via B4 Relay wrote:
>> > This series adds support for the CPU PMU in the new M3, M4 and A18 SoCs
>> > presed in apple devices. These PMUs have new encodings for events, along
>> > with larger codes for these events. All of these events are as Apple
>> > describes them in the various kpep files found under /usr/share/kpep on
>> > macOS 27. More events may exist, but we have no idea of their affinity,
>> > or what they actually count, so we don't include them here.
>> >
>> > These patches have been tested on my own M2 (t8133-j413) and M3
>> > (t6031-j514c) devices, as well as by Yuvan on their M4 (t8132-j713)
>> > device.
>> >
>> > If possible, the device tree changes should probably go through
>> > apple-soc, as this is where the recently picked up M4 Pro/Max dts are.
>> >
>> > Tested-by: Yuvan Shen <yuvanshen09@gmail.com> # on t8132-j713
>> > Signed-off-by: Myria Sarvay <myrialsarvay@gmail.com>
>> > ---
>> > Myria Sarvay (12):
>> > dt-bindings: arm: pmu: Add Apple M3/M4/A18 Pro SoC CPU PMU
> compatibles
>> > drivers/perf: apple_m1: Remove unused variables
>> > drivers/perf: apple_m1: Support per-implementation event size
>> > drivers/perf: apple_m1: Use macros for per-implementation init
> functions
>> > drivers/perf: apple_m1: Add Apple M3 Series Support
>> > drivers/perf: apple_m1: Add Apple M4 Series Support
>> > drivers/perf: apple_m1: Add Apple A18 Support
>> > arm64: dts: apple: t603x: Add PMU Device Nodes
>> > arm64: dts: apple: t8122: Add PMU Device Nodes
>> > arm64: dts: apple: t604x: Add PMU Device Nodes
>> > arm64: dts: apple: t8132: Add PMU Device Nodes
>> > arm64: dts: apple: t8140: Add PMU Device Nodes
>> >
>> Maybe the folder should be renamed to 'apple_arm' or something like
>> that?
>>
> What do you mean by this? What folder are you referring too? If you mean
> the device tree's, they're already under the arm64 folder, so apple_arm
> seems redundant. If you mean the CPU PMU name, I get that, but I'm not
> sure how to change that, given it's already hard coded with the config
> option `APPLE_M1_CPU_PMU`. I feel like changing its name at this point
> would cause backwards compatibility issues around kernel
> configs/blacklists if people use them.
Sorry, brain fart. I meant the file apple_m1, to consider splitting
it up into multiple files. It's no big deal though :)
-Josh
prev parent reply other threads:[~2026-11-16 13:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:14 [PATCH 00/13] drivers/perf: apple_m1: Add M3/M4/A18 Pro Support Myria Sarvay via B4 Relay
2026-11-03 10:14 ` [PATCH 01/13] dt-bindings: arm: pmu: Add Apple M3/M4/A18 Pro SoC CPU PMU compatibles Myria Sarvay via B4 Relay
2026-11-03 10:19 ` sashiko-bot
2026-11-06 12:55 ` Krzysztof Kozlowski
2026-11-03 10:14 ` [PATCH 02/13] drivers/perf: apple_m1: Remove unused variables Myria Sarvay via B4 Relay
2026-11-03 10:21 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 03/13] drivers/perf: apple_m1: Support per-implementation event tables Myria Sarvay via B4 Relay
2026-11-03 10:22 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 04/13] drivers/perf: apple_m1: Support per-implementation event size Myria Sarvay via B4 Relay
2026-11-03 10:25 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 05/13] drivers/perf: apple_m1: Use macros for per-implementation init functions Myria Sarvay via B4 Relay
2026-11-03 10:31 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 06/13] drivers/perf: apple_m1: Add Apple M3 Series Support Myria Sarvay via B4 Relay
2026-11-03 10:37 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 07/13] drivers/perf: apple_m1: Add Apple M4 " Myria Sarvay via B4 Relay
2026-11-03 10:43 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 08/13] drivers/perf: apple_m1: Add Apple A18 Support Myria Sarvay via B4 Relay
2026-11-03 10:47 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 09/13] arm64: dts: apple: t603x: Add PMU Device Nodes Myria Sarvay via B4 Relay
2026-11-03 10:54 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 10/13] arm64: dts: apple: t8122: " Myria Sarvay via B4 Relay
2026-11-03 11:03 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 11/13] arm64: dts: apple: t604x: " Myria Sarvay via B4 Relay
2026-11-03 11:12 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 12/13] arm64: dts: apple: t8132: " Myria Sarvay via B4 Relay
2026-11-03 11:14 ` sashiko-bot
2026-11-03 10:14 ` [PATCH 13/13] arm64: dts: apple: t8140: " Myria Sarvay via B4 Relay
2026-11-03 11:23 ` sashiko-bot
2026-11-08 17:32 ` [PATCH 00/13] drivers/perf: apple_m1: Add M3/M4/A18 Pro Support Joshua Peisach
[not found] ` <CAFTKyQziVo3COsPZSSZOaFs7R6HhXEWNHYfgTkjyACc7bkoBDw@mail.gmail.com>
2026-11-16 13:26 ` Joshua Peisach [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=DMWO4APJSZPS.16AA1EABR1AEJ@ubuntu.com \
--to=jpeisach@ubuntu.com \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=myrialsarvay@gmail.com \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=sven@kernel.org \
--cc=towinchenmi@gmail.com \
--cc=will@kernel.org \
--cc=yuvanshen09@gmail.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