From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Russell King <rmk@arm.linux.org.uk>,
Andrew Morton <akpm@osdl.org>
Subject: [patchset] Generic IRQ Subsystem: -V5
Date: Fri, 19 May 2006 16:52:25 +0200 [thread overview]
Message-ID: <20060519145225.GA12703@elte.hu> (raw)
In-Reply-To: 20060517221536.GA13444@elte.hu
This is Version 5 of the genirq patch-queue, against 2.6.17-rc4. The
genirq patch-queue improves the generic IRQ layer to be truly generic,
by adding various abstractions and features to it, without impacting
existing functionality. It converts ARM, i386 and x86_64 to this new
generic IRQ layer - while keeping compatibility with all the other
genirq architectures too.
The full patch-queue can be downloaded from:
http://redhat.com/~mingo/generic-irq-subsystem/
genirq -V5 is mostly about fixes and smaller cleanups. Suggestions from
many people were included - let us know if anything is missing. It has
been tested on i386, x86_64 and ARM systems.
Changes since -V4:
- fix: added IRQ_INPROGRESS protection to the fastack, level and simple
flow handlers, to avoid irq reentry due to hardware bugs. (especially
on SMP this is not unheard of.)
- fix: fixed two old-style IRQ probing bugs on non-irqchip
architectures.
- fix: bad irq vectors should increase the IRQ kstat too
- feature: added IRQ_DELAYED_DISABLE support for edge-irq handling on
really dumb controllers.
- docs: various documentation and comment updates
- cleanup/speedup: cleaned up desc->depth and IRQ_DISABLED handling -
the two were not always in sync. Made the generic flow handlers use
IRQ_DISABLED instead of desc->depth - results in more optimal code.
- cleanup: introduced generic_handle_irq(irq) for architectures to call
when they want the generic layer to handle an interrupt.
- rename: renamed probe_lock to probing_active
- rename: renamed handle_level_irq_fastack to handle_fastack_irq -
there is no strict requirement of the trigger type of the irq.
The split-out queue can be found at:
http://redhat.com/~mingo/generic-irq-subsystem/patches/
Ingo, Thomas
next prev parent reply other threads:[~2006-05-19 14:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 0:13 [patch 00/50] genirq: -V3 Ingo Molnar
2006-05-17 6:11 ` Benjamin Herrenschmidt
2006-05-17 22:27 ` Russell King
2006-05-18 0:32 ` Benjamin Herrenschmidt
2006-05-18 7:38 ` Russell King
2006-05-18 9:33 ` Benjamin Herrenschmidt
2006-05-17 22:15 ` [patchset] Generic IRQ Subsystem: -V4 Ingo Molnar
2006-05-18 22:24 ` Ingo Oeser
2006-05-19 9:31 ` Ingo Molnar
2006-05-19 17:00 ` Ingo Oeser
2006-05-19 14:52 ` Ingo Molnar [this message]
2006-06-07 16:54 ` [patchset] Generic IRQ Subsystem: -V5 Russell King
2006-06-07 17:20 ` Thomas Gleixner
2006-06-07 18:57 ` Thomas Gleixner
2006-06-08 11:35 ` Russell King
2006-06-08 12:04 ` [PATCH] genirq: Fix missing initializer for unmask in no_irq_chip Thomas Gleixner
2006-06-08 15:29 ` Russell King
2006-06-08 15:58 ` Thomas Gleixner
2006-06-08 18:57 ` Thomas Gleixner
2006-06-08 22:32 ` Thomas Gleixner
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=20060519145225.GA12703@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=tglx@linutronix.de \
/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