From: daniel.thompson@linaro.org (Daniel Thompson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3.17-rc4 v7 4/6] irqchip: gic: Add support for IPI FIQ
Date: Thu, 18 Sep 2014 14:20:48 -0700 [thread overview]
Message-ID: <541B4CB0.8040705@linaro.org> (raw)
In-Reply-To: <20140918081739.GA5182@n2100.arm.linux.org.uk>
On 18/09/14 01:17, Russell King - ARM Linux wrote:
> On Wed, Sep 17, 2014 at 09:10:16AM -0700, Daniel Thompson wrote:
>> @@ -604,8 +731,19 @@ static void gic_raise_softirq(const struct cpumask *mask, unsigned int irq)
>> {
>> int cpu;
>> unsigned long flags, map = 0;
>> + unsigned long softint;
>>
>> - raw_spin_lock_irqsave(&irq_controller_lock, flags);
>> + /*
>> + * The locking in this function ensures we don't use stale cpu mappings
>> + * and thus we never route an IPI to the wrong physical core during a
>> + * big.LITTLE switch. The switch code takes both of these locks meaning
>> + * we can choose whichever lock is safe to use from our current calling
>> + * context.
>> + */
>> + if (in_nmi())
>> + raw_spin_lock(&fiq_safe_migration_lock);
>> + else
>> + raw_spin_lock_irqsave(&irq_controller_lock, flags);
>
> BTW, I see this code is still here...
Quite so.
I'm afraid I haven't yet re-written it to use r/w locks (as proposed in
mails from the weekend) but I had to respin the default FIQ handler
patch to fix the CONFIG_FIQ build problem I introduced.
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, patches@linaro.org,
linaro-kernel@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sumit Semwal <sumit.semwal@linaro.org>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH 3.17-rc4 v7 4/6] irqchip: gic: Add support for IPI FIQ
Date: Thu, 18 Sep 2014 14:20:48 -0700 [thread overview]
Message-ID: <541B4CB0.8040705@linaro.org> (raw)
In-Reply-To: <20140918081739.GA5182@n2100.arm.linux.org.uk>
On 18/09/14 01:17, Russell King - ARM Linux wrote:
> On Wed, Sep 17, 2014 at 09:10:16AM -0700, Daniel Thompson wrote:
>> @@ -604,8 +731,19 @@ static void gic_raise_softirq(const struct cpumask *mask, unsigned int irq)
>> {
>> int cpu;
>> unsigned long flags, map = 0;
>> + unsigned long softint;
>>
>> - raw_spin_lock_irqsave(&irq_controller_lock, flags);
>> + /*
>> + * The locking in this function ensures we don't use stale cpu mappings
>> + * and thus we never route an IPI to the wrong physical core during a
>> + * big.LITTLE switch. The switch code takes both of these locks meaning
>> + * we can choose whichever lock is safe to use from our current calling
>> + * context.
>> + */
>> + if (in_nmi())
>> + raw_spin_lock(&fiq_safe_migration_lock);
>> + else
>> + raw_spin_lock_irqsave(&irq_controller_lock, flags);
>
> BTW, I see this code is still here...
Quite so.
I'm afraid I haven't yet re-written it to use r/w locks (as proposed in
mails from the weekend) but I had to respin the default FIQ handler
patch to fix the CONFIG_FIQ build problem I introduced.
next prev parent reply other threads:[~2014-09-18 21:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 16:10 [PATCH 3.17-rc4 v7 0/6] arm: Implement arch_trigger_all_cpu_backtrace Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-09-17 16:10 ` [PATCH 3.17-rc4 v7 1/6] ARM: remove unused do_unexp_fiq() function Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-09-17 16:10 ` [PATCH 3.17-rc4 v7 2/6] arm: fiq: Replace default FIQ handler Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-09-17 16:10 ` [PATCH 3.17-rc4 v7 3/6] arm64: Introduce dummy version of asm/fiq.h Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-09-22 9:16 ` Catalin Marinas
2014-09-22 9:16 ` Catalin Marinas
2014-09-17 16:10 ` [PATCH 3.17-rc4 v7 4/6] irqchip: gic: Add support for IPI FIQ Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-09-17 18:51 ` Russell King - ARM Linux
2014-09-17 18:51 ` Russell King - ARM Linux
2014-09-17 20:12 ` Daniel Thompson
2014-09-17 20:12 ` Daniel Thompson
2014-09-17 21:07 ` Russell King - ARM Linux
2014-09-17 21:07 ` Russell King - ARM Linux
2014-09-18 7:48 ` Russell King - ARM Linux
2014-09-18 7:48 ` Russell King - ARM Linux
2014-09-18 21:46 ` Marc Zyngier
2014-09-18 21:46 ` Marc Zyngier
2014-09-18 8:17 ` Russell King - ARM Linux
2014-09-18 8:17 ` Russell King - ARM Linux
2014-09-18 21:20 ` Daniel Thompson [this message]
2014-09-18 21:20 ` Daniel Thompson
2014-09-17 16:10 ` [PATCH 3.17-rc4 v7 5/6] ARM: add basic support for on-demand backtrace of other CPUs Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-09-17 16:10 ` [PATCH 3.17-rc4 v7 6/6] arm: smp: Handle ipi_cpu_backtrace() using FIQ (if available) Daniel Thompson
2014-09-17 16:10 ` Daniel Thompson
2014-10-14 22:37 ` [PATCH 3.17-rc4 v7 0/6] arm: Implement arch_trigger_all_cpu_backtrace Daniel Drake
2014-10-14 22:37 ` Daniel Drake
2014-10-14 23:31 ` Russell King - ARM Linux
2014-10-14 23:31 ` Russell King - ARM Linux
2014-10-16 9:33 ` Daniel Thompson
2014-10-16 9:33 ` Daniel Thompson
2014-11-04 17:05 ` Daniel Thompson
2014-11-04 17:05 ` Daniel Thompson
2014-11-04 17:19 ` Russell King - ARM Linux
2014-11-04 17:19 ` Russell King - ARM Linux
2014-10-16 9:23 ` Daniel Thompson
2014-10-16 9:23 ` Daniel Thompson
2014-10-16 12:23 ` Russell King - ARM Linux
2014-10-16 12:23 ` Russell King - ARM Linux
2014-10-16 13:15 ` Daniel Thompson
2014-10-16 13:15 ` Daniel Thompson
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=541B4CB0.8040705@linaro.org \
--to=daniel.thompson@linaro.org \
--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.