FW: [PATCH] MSI broke voyager build

From: Nguyen, Tom L (tom.l.nguyen_at_intel.com)
Date: 01/05/04

  • Next message: Ingo Oeser: "Re: [RFC,PATCH] use rcu for fasync_lock"
    Date:	Mon, 5 Jan 2004 13:19:02 -0800
    To: <linux-kernel@vger.kernel.org>
    
    

    Wednesday, December 31, 2003 2:59 PM, James Bottomley wrote:
    > The author made the arch/i386 compile depend on NR_VECTORS being
    > defined.
    >
    > This symbol, however, was put only into mach-default/irq_vectors.h
    >
    > The attached patch adds it to voyager; visws and pc9800 however, are
    > still broken.
    >
    > The code that breaks is this (in arch/i386/kernel/i8259.c):
    >
    > * us. (some of these will be overridden and become
    > * 'special' SMP interrupts)
    > */
    > - for (i = 0; i < NR_IRQS; i++) {
    > + for (i = 0; i < (NR_VECTORS - FIRST_EXTERNAL_VECTOR); i++) {
    > int vector = FIRST_EXTERNAL_VECTOR + i;
    > + if (i >= NR_IRQS)
    > + break;
    > if (vector != SYSCALL_VECTOR)
    > set_intr_gate(vector, interrupt[i]);
    >
    > as far as I can see, with NR_VECTORS set at 256, FIRST_EXTERNAL_VECTOR
    > at 32 and NR_IRQS set at 224 the two forms of the loop are identical.
    > The only case it would make a difference would be for NR_IRQ >
    > NR_VECTORS + FIRST_EXTERNAL_VECTOR which doesn't seem to make any
    > sense. Perhaps just backing this change out of i8259.c would be
    > better? NR_VECTORS seems to have no other defined use in the MSI code.

    >> It would make a significant difference when CONFIG_PCI_USE_VECTOR is
    >> set to "Y" by users to enable MSI support. The setting of
    >> CONFIG_PCI_USE_VECTOR to "Y" sets NR_IRQS at 239 (FIRST_SYSTEM_VECTOR)
    >> instead of 224.

    > ===== include/asm-i386/mach-voyager/irq_vectors.h 1.4 vs edited =====
    > --- 1.4/include/asm-i386/mach-voyager/irq_vectors.h Wed Oct 22 11:34:51
    > 2003
    > +++ edited/include/asm-i386/mach-voyager/irq_vectors.h Wed Dec 31
    > 16:30:15 2003
    > @@ -55,6 +55,7 @@
    > #define VIC_CPU_BOOT_CPI VIC_CPI_LEVEL0
    > #define VIC_CPU_BOOT_ERRATA_CPI (VIC_CPI_LEVEL0 + 8)
    >
    > +#define NR_VECTORS 256
    > #define NR_IRQS 224
    > #define NR_IRQ_VECTORS NR_IRQS
    >

    >> Thanks for providing a fix. The fix looks fine to me.

    Thanks,
    Long
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Ingo Oeser: "Re: [RFC,PATCH] use rcu for fasync_lock"

    Relevant Pages

    • Re: [CFT][PATCH] 2.6.4-rc1 remove x86 boot page tables
      ... > For VISWS I think you actually need to turn paging off explicitly. ... The patch will need a few tweaks but it should be fairly straight forward. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [PATCH] MSI broke voyager build
      ... The attached patch adds it to voyager; visws and pc9800 however, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 3/2] Clean up asm/pgalloc.h include
      ... This patch cleans up needless includes of asm/pgalloc.h from the ... Compile tested on x86_pc SMP. ... VISWS + SMP is an invalid configuration.] ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: [parisc-linux] Re: [PATCH 3/9] mm: parisc pte atomicity
      ... using your own tmpalias area sounds much better than getting ... I've simply not wrapped my head around the races, ... it looks like we agree that my patch is necessary and valid as is; ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: keyboard - was: Re: Linux 2.6.0-test4
      ... >> I was able to get the key unstuck by switching back and forth between ... I rebuild my kernel including your patch; ... I'll get back to you once I verify that the problem doesn't occur ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)