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>,
Christoph Hellwig <hch@infradead.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: [patch 00/50] genirq: -V3
Date: Wed, 17 May 2006 02:13:10 +0200 [thread overview]
Message-ID: <20060517001310.GA12877@elte.hu> (raw)
This is version 3 of the genirq patch-queue, against 2.6.17-rc4. This
patch-queue improves the generic IRQ layer to be truly generic, by
adding various abstractions and features to it, without impacting
existing functionality. It was written by Thomas Gleixner (who has done
most of the heavy-lifting) and me. We reused many bits of code and many
concepts from Russell King's ARM IRQ layer.
The ARM architecture has been updated to make use of this improved
generic IRQ layer. The new code also enables a cleaner and simpler
implementation of lowlevel irq-chip details, chained handlers and other
highlevel irq-flow handlers.
The patch-queue consists of 50 individual patches. The queue begins with
a handful of cleanups, to make sure we are adding features to a cleaned
up codebase. Then come the features that dont need the irq-chip
abstractions but are necessary extensions, then comes the core irq-chip
abstraction (genirq-core), features that rely on it, and finally, the
conversion of the ARM architecture to the new generic IRQ layer.
The full patch-queue can also be downloaded from:
http://redhat.com/~mingo/generic-irq-subsystem/
It has been build-tested with allyesconfig, and booted on x86, x86_64
and various ARM platforms. It has been build-tested on all the 50 ARM
platforms. Current ARM testing results are at:
http://www.linutronix.de/index.php?page=46
Many thanks to the ARM developers who ran the initial patches on their
ARM boards and helped tracking down initial migration bugs.
Review suggestions for past iterations of this code from Andrew Morton,
Benjamin Herrenschmidt and Christoph Hellwig were incorporated in this
version.
Comments, suggestions welcome,
Ingo, Thomas
next reply other threads:[~2006-05-17 0:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 0:13 Ingo Molnar [this message]
2006-05-17 6:11 ` [patch 00/50] genirq: -V3 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 ` [patchset] Generic IRQ Subsystem: -V5 Ingo Molnar
2006-06-07 16:54 ` 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=20060517001310.GA12877@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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