Jan, Best approach is to enable/disable MSI Interrupt on the fly. We are not supporting that feature currently. Something like setting DMA mask through probe code, we should enable/disable MSI interrupt through init code. Eventually, If MSI enable/disable is not on the fly, it will be always better to keep in default disable in module para of driver. - Kashyap -----Original Message----- From: Jan Beulich [mailto:jbeulich@xxxxxxxxxx] Sent: Tuesday, March 10, 2009 7:12 PM To: Desai, Kashyap Cc: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx; yinghai@xxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx Subject: RE: MSI override changes in mptbase >>> "Desai, Kashyap" <Kashyap.Desai@xxxxxxx> 10.03.09 13:12 >>> >Default behavior for all 3 buses (FC, SPI, and SAS) with respect to MSI is OFF. It is up to user, whether they want to enable/disable >MSI. Why is that change in behavior for SAS needed then? Thanks, Jan No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.11.9/1989 - Release Date: 03/07/09 18:43:00 -- 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
