Skip to contentSkip to conversation

MSI override changes in mptbase

DISCUSSION Jan Beulich 2 participants 2 messages Mar 10, 2009 – Mar 12, 2009 2 messages not in the archive SCSI

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 2 lines
Quoted 1 line
Quoted 1 line

"Desai, Kashyap" <[email protected]> 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

#3 lore raw

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:[email protected]]
Sent: Tuesday, March 10, 2009 7:12 PM
To: Desai, Kashyap
Cc: [email protected]; [email protected]; [email protected]
Subject: RE: MSI override changes in mptbase

Quoted 2 lines
Quoted 1 line
Quoted 1 line

"Desai, Kashyap" <[email protected]> 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