From: bigeasy@linutronix.de (Sebastian Andrzej Siewior)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/3] arm64: Allow forced irq threading
Date: Thu, 14 May 2015 17:40:41 +0200 [thread overview]
Message-ID: <20150514154041.GC13442@linutronix.de> (raw)
In-Reply-To: <1430167990-12333-3-git-send-email-anders.roxell@linaro.org>
* Anders Roxell | 2015-04-27 22:53:09 [+0200]:
>Now its safe to allow forced interrupt threading for arm64,
>all timer interrupts and the perf interrupt are marked NO_THREAD, as is
>the case with arch/arm: da0ec6f ARM: 7814/2: Allow forced irq threading
>
>Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Please, could this go via the ARM64 tree?
>---
> arch/arm64/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>index 9532f8d..3708eec 100644
>--- a/arch/arm64/Kconfig
>+++ b/arch/arm64/Kconfig
>@@ -61,6 +61,7 @@ config ARM64
> select HAVE_RCU_TABLE_FREE
> select HAVE_SYSCALL_TRACEPOINTS
> select IRQ_DOMAIN
>+ select IRQ_FORCED_THREADING
> select MODULES_USE_ELF_RELA
> select NO_BOOTMEM
> select OF
Sebastian
next prev parent reply other threads:[~2015-05-14 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 20:53 [PATCHv2 0/3] Enable PREEMPT_RT_FULL on arm64 Anders Roxell
2015-04-27 20:53 ` [PATCHv2 1/3] arm64: Mark PMU interrupt IRQF_NO_THREAD Anders Roxell
2015-05-14 15:39 ` Sebastian Andrzej Siewior
2015-05-14 15:42 ` Will Deacon
2015-05-14 17:09 ` Kevin Hilman
2015-05-14 17:10 ` Will Deacon
2015-05-14 17:19 ` Kevin Hilman
2015-05-14 17:24 ` Catalin Marinas
2015-04-27 20:53 ` [PATCHv2 2/3] arm64: Allow forced irq threading Anders Roxell
2015-05-14 15:40 ` Sebastian Andrzej Siewior [this message]
2015-04-27 20:53 ` [PATCHv2 3/3] arch/arm64: Enable PREEMPT_RT_FULL Anders Roxell
2015-05-14 15:57 ` Sebastian Andrzej Siewior
2015-05-15 12:08 ` Anders Roxell
2015-05-18 7:18 ` Sebastian Andrzej Siewior
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=20150514154041.GC13442@linutronix.de \
--to=bigeasy@linutronix.de \
--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).