From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] genirq: handling GIC per-cpu interrupts
Date: Tue, 18 Oct 2011 13:39:00 +0100 [thread overview]
Message-ID: <4E9D7364.2020209@arm.com> (raw)
In-Reply-To: <20111013181415.GM21648@n2100.arm.linux.org.uk>
On 13/10/11 19:14, Russell King - ARM Linux wrote:
> On Mon, Oct 03, 2011 at 06:04:02PM +0100, Marc Zyngier wrote:
>> The current GIC per-cpu interrupts (aka PPIs) suffer from a number of
>> problems:
>>
>> - They use a completely separate scheme to handle the interrupts,
>> mostly because the PPI concept doesn't really match the kernel view
>> of an interrupt.
>> - PPIs can only be used by the timer code, unless we add more low-level
>> assembly code.
>> - The local timer code can only be used by devices generating PPIs,
>> and not SPIs.
>> - At least one platform (msm) has started implementing its own
>> alternative scheme.
>> - Some low-level code gets duplicated, as usual...
>>
>> The proposed solution is to handle the PPIs using the same path as
>> SPIs. A new core API is added to deal with per-cpu interrupts in a
>> less awkward way. The local timer code is updated to reflect these
>> changes.
>>
>> The core API changes are based on an initial idea by Thomas Gleixner.
>>
>> Tested on ARM Versatile Express (Cortex A15), ARM RealView PB11MP,
>> OMAP4 (Panda) and Tegra (Harmony). Patch series against next-20110930.
>>
>> The two first patches can also be found in Thomas' tree:
>>
>> git://tesla.tglx.de/git/linux-2.6-tip irq/core
>
> So, how do we deal with merging this without ending up with some
> problematical inter-tree dependencies?
>
> It looks like I'll see conflicts with:
> arch/arm/common/gic.c
> arch/arm/kernel/smp.c
> arch/arm/include/asm/localtimer.h
>
> and possibly:
> arch/arm/include/asm/smp.h
> arch/arm/kernel/irq.c
>
> as well. I've not checked with patch 4, so there may be some more too.
>
> Some of this is probably because of 7123/1 and 7124/1.
I've set up a branch based on your "smp" branch, resolving the above
conflicts:
git://github.com/mzyngier/arm-platforms.git ppi-for-rmk
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2011-10-18 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 17:04 [PATCH v4 0/4] genirq: handling GIC per-cpu interrupts Marc Zyngier
2011-10-03 17:04 ` [PATCH v4 1/4] genirq: Add support for per-cpu dev_id interrupts Marc Zyngier
2011-10-03 17:04 ` [PATCH v4 2/4] genirq: percpu: allow interrupt type to be set at enable time Marc Zyngier
2011-10-03 17:04 ` [PATCH v4 3/4] ARM: gic: consolidate PPI handling Marc Zyngier
2011-10-03 17:04 ` [PATCH v4 4/4] ARM: gic, local timers: use the request_percpu_irq() interface Marc Zyngier
2011-10-13 18:14 ` [PATCH v4 0/4] genirq: handling GIC per-cpu interrupts Russell King - ARM Linux
2011-10-14 12:41 ` Marc Zyngier
2011-10-18 12:39 ` Marc Zyngier [this message]
2011-10-20 7:37 ` Shawn Guo
2011-10-20 8:21 ` Russell King - ARM Linux
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=4E9D7364.2020209@arm.com \
--to=marc.zyngier@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).