From: jamie.iles@picochip.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: perf-events: request PMU interrupts with IRQF_NOBALANCING
Date: Thu, 25 Feb 2010 12:31:45 +0000 [thread overview]
Message-ID: <20100225123145.GA4453@wear.picochip.com> (raw)
In-Reply-To: <1267099938-5555-1-git-send-email-will.deacon@arm.com>
On Thu, Feb 25, 2010 at 12:12:18PM +0000, Will Deacon wrote:
> If IRQ balancing is used on a multicore ARM system, PMU interrupt
> lines may be relocated onto CPUs other than the one causing the
> counter overflow. This can result in misattribution of events to
> the wrong core and, in the case that the CPU handling the interrupt
> has not experience counter overflow, the interrupt can be disabled
> because the handler returns IRQ_NONE.
>
> This patch adds the IRQF_NOBALANCING flag to the request_irq call
> in perf_events.c.
>
> Cc: Jamie Iles <jamie.iles@picochip.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
> arch/arm/kernel/perf_event.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/kernel/perf_event.c b/arch/arm/kernel/perf_event.c
> index c54ceb3..b44d159 100644
> --- a/arch/arm/kernel/perf_event.c
> +++ b/arch/arm/kernel/perf_event.c
> @@ -332,7 +332,8 @@ armpmu_reserve_hardware(void)
>
> for (i = 0; i < pmu_irqs->num_irqs; ++i) {
> err = request_irq(pmu_irqs->irqs[i], armpmu->handle_irq,
> - IRQF_DISABLED, "armpmu", NULL);
> + IRQF_DISABLED | IRQF_NOBALANCING,
> + "armpmu", NULL);
> if (err) {
> pr_warning("unable to request IRQ%d for ARM "
> "perf counters\n", pmu_irqs->irqs[i]);
> --
> 1.6.3.3
Hi Will,
Looks good to me.
Acked-by: Jamie Iles <jamie.iles@picochip.com>
Jamie
prev parent reply other threads:[~2010-02-25 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 12:12 [PATCH] ARM: perf-events: request PMU interrupts with IRQF_NOBALANCING Will Deacon
2010-02-25 12:31 ` Jamie Iles [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=20100225123145.GA4453@wear.picochip.com \
--to=jamie.iles@picochip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).