[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1268387091.10129.5973.camel@zakaz.uk.xensource.com>
Date: Fri, 12 Mar 2010 09:44:51 +0000
From: Ian Campbell <Ian.Campbell@...rix.com>
To: <linux-kernel@...r.kernel.org>
CC: Yinghai Lu <yinghai@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
"x86@...nel.org" <x86@...nel.org>,
"linuxppc-dev@...abs.org" <linuxppc-dev@...abs.org>
Subject: [GITPULL+PATCH 0/2] irq: move some interrupt arch_* functions into
struct irq_chip.
This small series ensures that struct irq_desc->chip_data is available
for alternative irq_chip implementations.
There is an outstanding issue wrt when/how the chip_data field is
initialised. I am continuing to investigate this but the solution is not
turning out as easy/low-impact as expected.
Since last time I've dropped the renaming portion of the series since it
was basically wrong, the functions I'd implicated as ioapic specific are
not at all.
Ian.
The following changes since commit 1ebbdcc83e75697c0d75eb091df172b7d93c84c1:
Ingo Molnar (1):
Merge branch 'perf/urgent'
are available in the git repository at:
git://xenbits.xensource.com/people/ianc/linux-2.6.git for-x86/irq
Ian Campbell (2):
irq: move some interrupt arch_* functions into struct irq_chip.
x86: irq_desc->chip_data is always correct whether or not SPARSE_IRQ is enabled.
arch/powerpc/kernel/irq.c | 2 +-
arch/x86/include/asm/hw_irq.h | 11 ++++++-
arch/x86/kernel/apic/io_apic.c | 61 ++++++++++++++++++++++++++++++++++-----
arch/x86/kernel/uv_irq.c | 5 +++
include/linux/interrupt.h | 2 +-
include/linux/irq.h | 12 +++++--
kernel/irq/handle.c | 2 +-
kernel/irq/numa_migrate.c | 12 ++++++-
kernel/softirq.c | 3 +-
9 files changed, 90 insertions(+), 20 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists