From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/11] arm: perf: parse cpu affinity from dt
Date: Mon, 17 Nov 2014 11:20:35 +0000 [thread overview]
Message-ID: <20141117112033.GF18061@arm.com> (raw)
In-Reply-To: <1415377536-12841-10-git-send-email-mark.rutland@arm.com>
On Fri, Nov 07, 2014 at 04:25:34PM +0000, Mark Rutland wrote:
> The current way we read interrupts form devicetree assumes that
> interrupts are in increasing order of logical cpu id (MPIDR.Aff{2,1,0}),
> and that these logical ids are in a contiguous block. This may not be
> the case in general - after a kexec cpu ids may be arbitrarily assigned,
> and multi-cluster systems do not have a contiguous range of cpu ids.
>
> This patch parses cpu affinity information for interrupts from an
> optional "interrupts-affinity" devicetree property described in the
> devicetree binding document. Support for existing dts and board files
> remains.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> ---
> arch/arm/include/asm/pmu.h | 12 +++
> arch/arm/kernel/perf_event_cpu.c | 196 +++++++++++++++++++++++++++++----------
> 2 files changed, 161 insertions(+), 47 deletions(-)
>
> diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h
> index b630a44..92fc1da 100644
> --- a/arch/arm/include/asm/pmu.h
> +++ b/arch/arm/include/asm/pmu.h
> @@ -12,6 +12,7 @@
> #ifndef __ARM_PMU_H__
> #define __ARM_PMU_H__
>
> +#include <linux/cpumask.h>
> #include <linux/interrupt.h>
> #include <linux/perf_event.h>
>
> @@ -89,6 +90,15 @@ struct pmu_hw_events {
> struct arm_pmu *percpu_pmu;
> };
>
> +/*
> + * For systems with heterogeneous PMUs, we need to know which CPUs each
> + * (possibly percpu) IRQ targets. Map between them with an array of these.
> + */
> +struct cpu_irq {
> + cpumask_t cpus;
> + int irq;
> +};
> +
> struct arm_pmu {
> struct pmu pmu;
> cpumask_t active_irqs;
> @@ -118,6 +128,8 @@ struct arm_pmu {
> struct platform_device *plat_device;
> struct pmu_hw_events __percpu *hw_events;
> struct notifier_block hotplug_nb;
> + int nr_irqs;
> + struct cpu_irq *irq_map;
> };
>
> #define to_arm_pmu(p) (container_of(p, struct arm_pmu, pmu))
> diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c
> index dfcaba5..f09c8a0 100644
> --- a/arch/arm/kernel/perf_event_cpu.c
> +++ b/arch/arm/kernel/perf_event_cpu.c
> @@ -85,20 +85,27 @@ static void cpu_pmu_free_irq(struct arm_pmu *cpu_pmu)
> struct platform_device *pmu_device = cpu_pmu->plat_device;
> struct pmu_hw_events __percpu *hw_events = cpu_pmu->hw_events;
>
> - irqs = min(pmu_device->num_resources, num_possible_cpus());
> + irqs = cpu_pmu->nr_irqs;
>
> - irq = platform_get_irq(pmu_device, 0);
> - if (irq >= 0 && irq_is_percpu(irq)) {
> - on_each_cpu(cpu_pmu_disable_percpu_irq, &irq, 1);
> - free_percpu_irq(irq, &hw_events->percpu_pmu);
> - } else {
> - for (i = 0; i < irqs; ++i) {
> - if (!cpumask_test_and_clear_cpu(i, &cpu_pmu->active_irqs))
> - continue;
> - irq = platform_get_irq(pmu_device, i);
> - if (irq >= 0)
> - free_irq(irq, per_cpu_ptr(&hw_events->percpu_pmu, i));
> + for (i = 0; i < irqs; i++) {
> + struct cpu_irq *map = &cpu_pmu->irq_map[i];
> + irq = map->irq;
> +
> + if (irq <= 0)
> + continue;
> +
> + if (irq_is_percpu(irq)) {
> + on_each_cpu(cpu_pmu_disable_percpu_irq, &irq, 1);
Hmm, ok, so we're assuming that all the PMUs will be wired with PPIs in this
case. I have a patch allowing per-cpu interrupts to be requested for a
cpumask, but I suppose that can wait until it's actually needed.
Will
WARNING: multiple messages have this Message-ID (diff)
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 09/11] arm: perf: parse cpu affinity from dt
Date: Mon, 17 Nov 2014 11:20:35 +0000 [thread overview]
Message-ID: <20141117112033.GF18061@arm.com> (raw)
In-Reply-To: <1415377536-12841-10-git-send-email-mark.rutland@arm.com>
On Fri, Nov 07, 2014 at 04:25:34PM +0000, Mark Rutland wrote:
> The current way we read interrupts form devicetree assumes that
> interrupts are in increasing order of logical cpu id (MPIDR.Aff{2,1,0}),
> and that these logical ids are in a contiguous block. This may not be
> the case in general - after a kexec cpu ids may be arbitrarily assigned,
> and multi-cluster systems do not have a contiguous range of cpu ids.
>
> This patch parses cpu affinity information for interrupts from an
> optional "interrupts-affinity" devicetree property described in the
> devicetree binding document. Support for existing dts and board files
> remains.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> ---
> arch/arm/include/asm/pmu.h | 12 +++
> arch/arm/kernel/perf_event_cpu.c | 196 +++++++++++++++++++++++++++++----------
> 2 files changed, 161 insertions(+), 47 deletions(-)
>
> diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h
> index b630a44..92fc1da 100644
> --- a/arch/arm/include/asm/pmu.h
> +++ b/arch/arm/include/asm/pmu.h
> @@ -12,6 +12,7 @@
> #ifndef __ARM_PMU_H__
> #define __ARM_PMU_H__
>
> +#include <linux/cpumask.h>
> #include <linux/interrupt.h>
> #include <linux/perf_event.h>
>
> @@ -89,6 +90,15 @@ struct pmu_hw_events {
> struct arm_pmu *percpu_pmu;
> };
>
> +/*
> + * For systems with heterogeneous PMUs, we need to know which CPUs each
> + * (possibly percpu) IRQ targets. Map between them with an array of these.
> + */
> +struct cpu_irq {
> + cpumask_t cpus;
> + int irq;
> +};
> +
> struct arm_pmu {
> struct pmu pmu;
> cpumask_t active_irqs;
> @@ -118,6 +128,8 @@ struct arm_pmu {
> struct platform_device *plat_device;
> struct pmu_hw_events __percpu *hw_events;
> struct notifier_block hotplug_nb;
> + int nr_irqs;
> + struct cpu_irq *irq_map;
> };
>
> #define to_arm_pmu(p) (container_of(p, struct arm_pmu, pmu))
> diff --git a/arch/arm/kernel/perf_event_cpu.c b/arch/arm/kernel/perf_event_cpu.c
> index dfcaba5..f09c8a0 100644
> --- a/arch/arm/kernel/perf_event_cpu.c
> +++ b/arch/arm/kernel/perf_event_cpu.c
> @@ -85,20 +85,27 @@ static void cpu_pmu_free_irq(struct arm_pmu *cpu_pmu)
> struct platform_device *pmu_device = cpu_pmu->plat_device;
> struct pmu_hw_events __percpu *hw_events = cpu_pmu->hw_events;
>
> - irqs = min(pmu_device->num_resources, num_possible_cpus());
> + irqs = cpu_pmu->nr_irqs;
>
> - irq = platform_get_irq(pmu_device, 0);
> - if (irq >= 0 && irq_is_percpu(irq)) {
> - on_each_cpu(cpu_pmu_disable_percpu_irq, &irq, 1);
> - free_percpu_irq(irq, &hw_events->percpu_pmu);
> - } else {
> - for (i = 0; i < irqs; ++i) {
> - if (!cpumask_test_and_clear_cpu(i, &cpu_pmu->active_irqs))
> - continue;
> - irq = platform_get_irq(pmu_device, i);
> - if (irq >= 0)
> - free_irq(irq, per_cpu_ptr(&hw_events->percpu_pmu, i));
> + for (i = 0; i < irqs; i++) {
> + struct cpu_irq *map = &cpu_pmu->irq_map[i];
> + irq = map->irq;
> +
> + if (irq <= 0)
> + continue;
> +
> + if (irq_is_percpu(irq)) {
> + on_each_cpu(cpu_pmu_disable_percpu_irq, &irq, 1);
Hmm, ok, so we're assuming that all the PMUs will be wired with PPIs in this
case. I have a patch allowing per-cpu interrupts to be requested for a
cpumask, but I suppose that can wait until it's actually needed.
Will
next prev parent reply other threads:[~2014-11-17 11:20 UTC|newest]
Thread overview: 42+ 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 ` 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 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 02/11] perf: allow for PMU-specific event filtering Mark Rutland
2014-11-07 16:25 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 03/11] arm: perf: treat PMUs as CPU affine Mark Rutland
2014-11-07 16:25 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 04/11] arm: perf: filter unschedulable events Mark Rutland
2014-11-07 16:25 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 05/11] arm: perf: reject multi-pmu groups Mark Rutland
2014-11-07 16:25 ` 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 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 07/11] arm: perf: document PMU affinity binding Mark Rutland
2014-11-07 16:25 ` Mark Rutland
2014-11-17 11:14 ` Will Deacon
2014-11-17 11:14 ` Will Deacon
2014-11-17 14:32 ` Rob Herring
2014-11-17 14:32 ` Rob Herring
2014-11-17 15:01 ` Mark Rutland
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-07 16:25 ` Mark Rutland
2014-11-17 11:16 ` Will Deacon
2014-11-17 11:16 ` Will Deacon
2014-11-17 15:02 ` Mark Rutland
2014-11-17 15:02 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 09/11] arm: perf: parse cpu " Mark Rutland
2014-11-07 16:25 ` Mark Rutland
2014-11-17 11:20 ` Will Deacon [this message]
2014-11-17 11:20 ` Will Deacon
2014-11-17 15:08 ` Mark Rutland
2014-11-17 15:08 ` Mark Rutland
2014-11-18 10:40 ` Will Deacon
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 ` Mark Rutland
2014-11-07 16:25 ` [PATCH 11/11] arm: dts: vexpress: describe all PMUs in TC2 dts Mark Rutland
2014-11-07 16:25 ` Mark Rutland
2014-11-17 11:24 ` [PATCH 00/11] arm: perf: add support for heterogeneous PMUs Will Deacon
2014-11-17 11:24 ` 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=20141117112033.GF18061@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.