From: Will Deacon <will.deacon@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 07/11] arm: perf: document PMU affinity binding
Date: Mon, 17 Nov 2014 11:14:50 +0000 [thread overview]
Message-ID: <20141117111450.GD18061@arm.com> (raw)
In-Reply-To: <1415377536-12841-8-git-send-email-mark.rutland@arm.com>
Hi Mark,
On Fri, Nov 07, 2014 at 04:25:32PM +0000, Mark Rutland wrote:
> To describe the various ways CPU PMU interrupts might be wired up, we
> can refer to the topology information in the device tree.
>
> This patch adds a new property to the PMU binding, interrupts-affinity,
> which describes the relationship between CPUs and interrupts. This
> information is necessary to handle systems with heterogeneous PMU
> implementations (e.g. big.LITTLE). Documentation is added describing the
> use of said property.
I'm not entirely comfortable with using interrupt affinity to convey
PMU affinity. It seems perfectly plausible for somebody to play the usual
trick of ORing all the irq lines together, despite having a big/little
PMU configuration.
Can you describe such a system with this binding?
> +Example 2 (Multiple clusters with single interrupts):
> +
> +cpus {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + CPU0: cpu@0 {
> + reg = <0x0>;
> + compatible = "arm,cortex-a15-pmu";
> + };
> +
> + CPU1: cpu@1 {
> + reg = <0x1>;
> + compatible = "arm,cotex-a15-pmu";
cortex
> + };
> +
> + CPU100: cpu@100 {
> + reg = <0x100>;
> + compatible = "arm,cortex-a7-pmu";
> + };
> +
> + cpu-map {
> + cluster0 {
> + CORE_0_0: core0 {
> + cpu = <&CPU0>;
> + };
> + CORE_0_1: core1 {
> + cpu = <&CPU1>;
> + };
> + };
> + cluster1 {
> + CORE_1_0: core0 {
> + cpu = <&CPU100>;
> + };
> + };
> + };
> +};
> +
> +pmu_a15 {
> + compatible = "arm,cortex-a15-pmu";
> + interrupts = <100>, <101>;
> + interrupts-affinity = <&CORE0>, <&CORE1>;
> +};
> +
> +pmu_a7 {
> + compatible = "arm,cortex-a7-pmu";
> + interrupts = <105>;
> + interrupts-affinity = <&CORE_1_0>;
> +};
> +
> +Example 3 (Multiple clusters with per-cpu interrupts):
> +
> +cpus {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + CPU0: cpu@0 {
> + reg = <0x0>;
> + compatible = "arm,cortex-a15-pmu";
> + };
> +
> + CPU1: cpu@1 {
> + reg = <0x1>;
> + compatible = "arm,cotex-a15-pmu";
Same here.
Will
next prev parent reply other threads:[~2014-11-17 11:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 16:25 [PATCH 00/11] arm: perf: add support for heterogeneous PMUs Mark Rutland
2014-11-07 16:25 ` [PATCH 01/11] of: Add empty of_get_next_parent stub Mark Rutland
2014-11-07 16:25 ` [PATCH 02/11] perf: allow for PMU-specific event filtering Mark Rutland
2014-11-07 16:25 ` [PATCH 03/11] arm: perf: treat PMUs as CPU affine Mark Rutland
2014-11-07 16:25 ` [PATCH 04/11] arm: perf: filter unschedulable events Mark Rutland
2014-11-07 16:25 ` [PATCH 05/11] arm: perf: reject multi-pmu groups Mark Rutland
2014-11-07 16:25 ` [PATCH 06/11] arm: perf: probe number of counters on affine CPUs Mark Rutland
2014-11-07 16:25 ` [PATCH 07/11] arm: perf: document PMU affinity binding Mark Rutland
2014-11-17 11:14 ` Will Deacon [this message]
2014-11-17 14:32 ` Rob Herring
2014-11-17 15:01 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 08/11] arm: perf: add functions to parse affinity from dt Mark Rutland
2014-11-17 11:16 ` Will Deacon
2014-11-17 15:02 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 09/11] arm: perf: parse cpu " Mark Rutland
2014-11-17 11:20 ` Will Deacon
2014-11-17 15:08 ` Mark Rutland
2014-11-18 10:40 ` Will Deacon
2014-11-07 16:25 ` [PATCH 10/11] arm: perf: remove singleton PMU restriction Mark Rutland
2014-11-07 16:25 ` [PATCH 11/11] arm: dts: vexpress: describe all PMUs in TC2 dts Mark Rutland
2014-11-17 11:24 ` [PATCH 00/11] arm: perf: add support for heterogeneous PMUs 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=20141117111450.GD18061@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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