linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [RFC PATCH v2 0/3] genirq: handling GIC per-cpu interrupts
@ 2011-09-16 13:50 Marc Zyngier
  2011-09-16 13:50 ` [RFC PATCH v2 1/3] genirq: add support for per-cpu dev_id interrupts Marc Zyngier
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Marc Zyngier @ 2011-09-16 13:50 UTC (permalink / raw)
  To: linux-arm-kernel

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 A5 and A15), ARM RealView
PB11MP, OMAP4 (Panda) and Tegra (Harmony). Patch series against
next-20110831.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-09-16 13:50 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-16 13:50 [RFC PATCH v2 0/3] genirq: handling GIC per-cpu interrupts Marc Zyngier
2011-09-16 13:50 ` [RFC PATCH v2 1/3] genirq: add support for per-cpu dev_id interrupts Marc Zyngier
2011-09-16 13:50 ` [RFC PATCH v2 2/3] ARM: gic: consolidate PPI handling Marc Zyngier
2011-09-16 13:50 ` [RFC PATCH v2 3/3] ARM: gic, local timers: use the request_percpu_irq() interface Marc Zyngier

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).