linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: Mark PMU interrupt IRQF_NO_THREAD
Date: Thu, 23 Apr 2015 11:46:25 +0100	[thread overview]
Message-ID: <20150423104624.GD1652@arm.com> (raw)
In-Reply-To: <1429628755-22492-2-git-send-email-anders.roxell@linaro.org>

On Tue, Apr 21, 2015 at 04:05:54PM +0100, Anders Roxell wrote:
> Mark the PMU interrupts as non-threadable, as is the case with
> arch/arm: d9c3365 ARM: 7813/1: Mark pmu interupt IRQF_NO_THREAD
> 
> Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
>  arch/arm64/kernel/perf_event.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Acked-by: Will Deacon <will.deacon@arm.com>

Catalin can queue this for 4.2.

Cheers,

Will

> diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
> index 195991d..7db5c84 100644
> --- a/arch/arm64/kernel/perf_event.c
> +++ b/arch/arm64/kernel/perf_event.c
> @@ -488,7 +488,7 @@ armpmu_reserve_hardware(struct arm_pmu *armpmu)
>  			}
>  
>  			err = request_irq(irq, armpmu->handle_irq,
> -					IRQF_NOBALANCING,
> +					IRQF_NOBALANCING | IRQF_NO_THREAD,
>  					"arm-pmu", armpmu);
>  			if (err) {
>  				pr_err("unable to request IRQ%d for ARM PMU counters\n",
> -- 
> 2.1.4
> 

  reply	other threads:[~2015-04-23 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 15:05 [PATCH 0/2] arm64: make it possible to enable threadirqs Anders Roxell
2015-04-21 15:05 ` [PATCH 1/2] arm64: Mark PMU interrupt IRQF_NO_THREAD Anders Roxell
2015-04-23 10:46   ` Will Deacon [this message]
2015-04-21 15:05 ` [PATCH 2/2] arm64: Allow forced irq threading Anders Roxell

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=20150423104624.GD1652@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 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).