From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Hector Martin <marcan@marcan.st>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dougall <dougallj@gmail.com>,
kernel-team@android.com
Subject: Re: [PATCH v5 00/10] drivers/perf: CPU PMU driver for Apple M1
Date: Mon, 07 Mar 2022 15:55:44 +0000 [thread overview]
Message-ID: <875yop21vj.wl-maz@kernel.org> (raw)
In-Reply-To: <20220208185604.1097957-1-maz@kernel.org>
On Tue, 08 Feb 2022 18:55:54 +0000,
Marc Zyngier <maz@kernel.org> wrote:
>
> The M1 SoC embeds a per-CPU PMU that has a very different programming
> interface compared to the architected PMUv3 that is normally present
> on standard implementations.
>
> This small series adds a driver for this HW by leveraging the arm_pmu
> infrastructure, resulting in a rather simple driver.
>
> Of course, we know next to nothing about the actual events this PMU
> counts, aside from CPU cycles and instructions. Everything else is
> undocumented (though as Dougall pointed out, someone could extract the
> relevant information from a macOS install if they wanted -- I don't).
> I'm looking at allowing the perf userspace tool to load the event
> descriptions at runtime, which would probably help.
[...]
FWIW, I have created two branches:
- [1] has the full series
- [2] has the irqchip/DT prefix of [1]
Both branches are stable, and I expect [2] to be used as a shared
branch between the irqchip and perf trees.
Thanks,
M.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=hack/m1-pmu
[2] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/aic-pmu
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Hector Martin <marcan@marcan.st>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dougall <dougallj@gmail.com>,
kernel-team@android.com
Subject: Re: [PATCH v5 00/10] drivers/perf: CPU PMU driver for Apple M1
Date: Mon, 07 Mar 2022 15:55:44 +0000 [thread overview]
Message-ID: <875yop21vj.wl-maz@kernel.org> (raw)
In-Reply-To: <20220208185604.1097957-1-maz@kernel.org>
On Tue, 08 Feb 2022 18:55:54 +0000,
Marc Zyngier <maz@kernel.org> wrote:
>
> The M1 SoC embeds a per-CPU PMU that has a very different programming
> interface compared to the architected PMUv3 that is normally present
> on standard implementations.
>
> This small series adds a driver for this HW by leveraging the arm_pmu
> infrastructure, resulting in a rather simple driver.
>
> Of course, we know next to nothing about the actual events this PMU
> counts, aside from CPU cycles and instructions. Everything else is
> undocumented (though as Dougall pointed out, someone could extract the
> relevant information from a macOS install if they wanted -- I don't).
> I'm looking at allowing the perf userspace tool to load the event
> descriptions at runtime, which would probably help.
[...]
FWIW, I have created two branches:
- [1] has the full series
- [2] has the irqchip/DT prefix of [1]
Both branches are stable, and I expect [2] to be used as a shared
branch between the irqchip and perf trees.
Thanks,
M.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=hack/m1-pmu
[2] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/aic-pmu
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-03-07 15:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 18:55 [PATCH v5 00/10] drivers/perf: CPU PMU driver for Apple M1 Marc Zyngier
2022-02-08 18:55 ` Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 01/10] dt-bindings: arm-pmu: Document Apple PMU compatible strings Marc Zyngier
2022-02-08 18:55 ` Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 02/10] dt-bindings: apple, aic: Add CPU PMU per-cpu pseudo-interrupts Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 02/10] dt-bindings: apple,aic: " Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 03/10] dt-bindings: apple, aic: Add affinity description for " Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 03/10] dt-bindings: apple,aic: " Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 04/10] irqchip/apple-aic: Parse FIQ affinities from device-tree Marc Zyngier
2022-02-08 18:55 ` Marc Zyngier
2022-02-08 18:55 ` [PATCH v5 05/10] irqchip/apple-aic: Wire PMU interrupts Marc Zyngier
2022-02-08 18:55 ` Marc Zyngier
2022-02-08 18:56 ` [PATCH v5 06/10] arm64: dts: apple: Add t8103 PMU interrupt affinities Marc Zyngier
2022-02-08 18:56 ` Marc Zyngier
2022-02-08 18:56 ` [PATCH v5 07/10] arm64: dts: apple: Add t8303 PMU nodes Marc Zyngier
2022-02-08 18:56 ` Marc Zyngier
2022-02-08 18:56 ` [PATCH v5 08/10] irqchip/apple-aic: Move PMU-specific registers to their own include file Marc Zyngier
2022-02-08 18:56 ` Marc Zyngier
2022-02-08 18:56 ` [PATCH v5 09/10] drivers/perf: arm_pmu: Handle 47 bit counters Marc Zyngier
2022-02-08 18:56 ` Marc Zyngier
2022-02-08 18:56 ` [PATCH v5 10/10] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver Marc Zyngier
2022-02-08 18:56 ` Marc Zyngier
2022-03-07 15:55 ` Marc Zyngier [this message]
2022-03-07 15:55 ` [PATCH v5 00/10] drivers/perf: CPU PMU driver for Apple M1 Marc Zyngier
2022-03-08 14:10 ` Will Deacon
2022-03-08 14:10 ` 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=875yop21vj.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=devicetree@vger.kernel.org \
--cc=dougallj@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sven@svenpeter.dev \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.