Messages in this thread | | | Subject | Re: 2.6.17-rc5-mm1 | From | Roland Dreier <> | Date | Tue, 30 May 2006 16:32:13 -0700 |
| |
> then i guess a quick solution would be to do: > > if (!irq_desc[irq].irq_handler) > __do_IRQ(irq, regs); > else > generic_handle_irq(irq, regs); > > in arch/x86_64/kernel/irq.c [and in arch/i386/kernel/irq.c], and > __do_IRQ() should handle the old-style irq-type MSI code just fine.
Indeed (fixing ".irq_handler" to be ".handle_irq"), with that change MSI-X works fine with ib_mthca on my system. The only slightly funny quirk is that the IRQ type is shown as "PCI-MSI-X-<NULL>", I guess because it's printing handle_irq_name(NULL).
However (as BenH pointed out) there's definitely some work to do to untangle MSI...
- R. - 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/
| |