David Howells (on Tue, 12 Sep 2006 17:27:14 +0100) wrote:
>
>Patch 3/3 seems to be stuck on the linux-arch mailing list and is either
>delayed or maybe has been discarded, probably due to its size (about a
>megabyte). It can be downloaded from here:
>
> http://people.redhat.com/~dhowells/irq-global-regs.diff.bz2
This blows up immediately on IA64.
GEN /build/kaos/2.6.18-irq-global/obj/Makefile
scripts/kconfig/conf -s arch/ia64/Kconfig
Using /build/kaos/2.6.18-irq-global/linux-2.6 as source for kernel
GEN /build/kaos/2.6.18-irq-global/obj/Makefile
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-ia64
CC arch/ia64/kernel/asm-offsets.s
In file included from include2/asm/hardirq.h:11,
from
/build/kaos/2.6.18-irq-global/linux-2.6/include/linux/hardirq.h:7,
from
/build/kaos/2.6.18-irq-global/linux-2.6/include/linux/interrupt.h:11,
from
/build/kaos/2.6.18-irq-global/linux-2.6/include/asm-ia64/mca.h:16,
from
/build/kaos/2.6.18-irq-global/linux-2.6/arch/ia64/kernel/asm-offsets.c:15:
/build/kaos/2.6.18-irq-global/linux-2.6/include/linux/irq.h:24:26: error:
asm/irq_regs.h: No such file or directory
Are you expecting the include path to automatically fallback to
include/asm-generic if a file does not exist in include/asm-$(ARCH)?
That does not happen.
Workaround with "cp include/asm-generic/irq_regs.h include/asm-ia64/",
then there are several compile errors in IA64 specific code, patches to
follow.
I am concerned about code that has been missed in this patch. For
example,
arch/ia64/kernel/perfmon.c:
static int
pfm_do_interrupt_handler(int irq, void *arg, struct pt_regs *regs)
BTW, this patch is going to cause major headaches for KDB, it uses
pt_regs all over the place. Having said that, I think the patch is
worthwhile. Tracking down the pt_regs in the register stack in an IA64
dump can be a major headache, using a global structure will make life
easier.
-
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
