Brian King wrote: > James Bottomley wrote: >> On Thu, 2009-05-21 at 14:51 -0500, James Bottomley wrote: >> I saw the quirk fix for this go by: >> >> http://ozlabs.org/pipermail/linuxppc-dev/2009-May/072436.html >> >> Is there an easy way to trigger an interrupt on this device? Preferably >> in ipr_probe_ioa() so we can at least print out if the interrupts are >> misrouted and fall back from MSI to normal using the PCI infrastructure? > > I just talked with one of the adapter firmware developers and it sounds like > this might be possible. I'll work with Wayne on coding something up to try. > > -Brian > I've put together some code to trigger the test MSI and either fall back to LSI if it isn't detected, or continue on using MSI. In the routine that does the setup and test I have this call to request_irq: rc = request_irq(pdev->irq, ipr_test_intr, 0, IPR_NAME, ioa_cfg); Note that the flags value is '0'. The question came up as to whether or not this value should really be IRQF_SHARED. Given that this is for an MSI interrupt and MSI interrupts are not shared by definition, IRQF_SHARED did not seem correct. What should the flags value be in this case? -- Wayne Boyer IBM - Beaverton, Oregon LTC S/W Development - eServerIO (503) 578-5236, T/L 775-5236 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
