From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2 v2] arm: Allow forced irq threading
Date: Wed, 14 Aug 2013 10:08:37 +0000 [thread overview]
Message-ID: <520B5725.7000907@ti.com> (raw)
In-Reply-To: <20130812200301.GB4181@breakpoint.cc>
On Monday 12 August 2013 08:03 PM, Sebastian Andrzej Siewior wrote:
> From: Thomas Gleixner <tglx@linutronix•de>
>
> All timer interrupts and the perf interrupt are marked NO_THREAD, so
> its safe to allow forced interrupt threading.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix•de>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
> ---
> On Thu, Feb 14, 2013 at 11:04:48PM +0100, Thomas Gleixner wrote:
>> On Thu, 14 Feb 2013, Russell King - ARM Linux wrote:
>>
>>> What effect does this have on IRQ latency, particularly on the slower CPUs?
>>
>> It does not affect anything unless you add "threadirqs" to the kernel
>> command line. This command line argument puts the kernel into forced
>> irq threading mode. Otherwise it just works as now.
>
> I reposted the patch since it no longer applies clean on v3.11-rc5. From what
> tglx explained, I don't think there are any outstanding issues, are there?
>
> arch/arm/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 43594d5..405e4c0 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -20,6 +20,7 @@ config ARM
> select GENERIC_STRNCPY_FROM_USER
> select GENERIC_STRNLEN_USER
> select HARDIRQS_SW_RESEND
> + select IRQ_FORCED_THREADING
Please add in alphabetic sorted order.
> select HAVE_ARCH_JUMP_LABEL if !XIP_KERNEL
> select HAVE_ARCH_KGDB
> select HAVE_ARCH_SECCOMP_FILTER
Thanks,
Sekhar
next prev parent reply other threads:[~2013-08-14 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 20:53 [patch 0/2] ARM: Allow forced irq threading Thomas Gleixner
2013-02-14 20:53 ` [patch 1/2] arm: Mark pmu interupt IRQF_NO_THREAD Thomas Gleixner
2013-02-15 9:51 ` Will Deacon
2013-08-12 19:52 ` Sebastian Andrzej Siewior
2013-08-13 11:11 ` Will Deacon
2013-08-14 9:52 ` Sebastian Andrzej Siewior
2013-02-14 20:53 ` [patch 2/2] arm: Allow forced irq threading Thomas Gleixner
2013-02-14 21:49 ` Russell King - ARM Linux
2013-02-14 22:04 ` Thomas Gleixner
2013-08-12 20:03 ` [PATCH 2/2 v2] " Sebastian Andrzej Siewior
2013-08-14 10:08 ` Sekhar Nori [this message]
2013-08-14 14:43 ` [PATCH 2/2 v3] " 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=520B5725.7000907@ti.com \
--to=nsekhar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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