Message Signaled Interrupts
Message Signaled Interrupts (MSI), in PCI 2.2 and later in PCI Express, are an alternative in-band method of signalling an interrupt. Traditionally, a device has an interrupt pin which it asserts when it wants to signal an interrupt to the host processing environment. This traditional form of interrupt signalling is an out-of-band form of control signalling since it uses a separate dedicated path relative to the main data path to send such control information. While PCI Express does not have separate interrupt pins, it has special in-band messages to allow it to emulate a pin assertion or deassertion. Message Signaled Interrupts allow the device to write a small amount of data to a special memory-mapped I/O address. The chipset will deliver the corresponding interrupt to a processor.
A common misconception with Message Signaled Interrupts is that they allow the device to send data to a processor as part of the interrupt. The data that is sent as part of the write is used by the chipset to determine which interrupt to trigger on which processor; it is not available for the device to communicate additional information to the interrupt handler.
Some non-PCI architectures also use Message Signaled Interrupts. For example, HP GSC devices do not have interrupt pins and can only interrupt by writing directly to the processor's interrupt register in memory space.
Advantages over pin-based out-of-band interrupt signalling
While more complex to implement in a device, MSI has some significant advantages.
On the mechanical side, fewer pins makes for a simpler, cheaper, and more reliable connector. While this is no advantage to the standard PCI connector, PCI Express takes advantage of these savings.
MSI increases the number of interrupts that are possible. While conventional PCI was limited to 4 interrupts per card (and, because they were shared among all cards, most used just one), message signaled interrupts allow dozens of interrupts per card, when that is useful.
There is also a slight performance advantage. In software, a pin-based interrupt could race with a posted write to memory. That is, the PCI device would write data to memory and then send an interrupt to indicate the DMA write was complete. However, a PCI bridge or memory controller might buffer the write in order to not interfere with some other memory use. The interrupt could arrive before the DMA write was complete, and the processor could read stale data from memory. To prevent this race, interrupt handlers were required to read from the device to ensure that the DMA write had finished. This read had a moderate performance penalty. An MSI write cannot pass a DMA write, so the race is eliminated.
PCI defines two optional extensions to support Message Signaled Interrupts, MSI and MSI-X. While PCI Express is compatible with legacy interrupts on the software level, it requires MSI or MSI-X.
MSI (first defined in PCI 2.2) permits a device to allocate 1, 2, 4, 8, 16 or 32 interrupts. The device is programmed with an address to write to (generally a control register in an interrupt controller), and a 16-bit data word to identify it. The interrupt number is added to the data word to identify the interrupt. Some platforms such as Windows do not use all 32 interrupts but only use up to 16 interrupts.
MSI-X (first defined in PCI 3.0) permits a device to allocate up to 2048 interrupts. The single address used by original MSI was found to be restrictive for some architectures. In particular, it made it difficult to target individual interrupts to different processors, which is helpful in some high-speed networking applications. MSI-X allows a larger number of interrupts and gives each one a separate target address and data word. Devices with MSI-X do not necessarily support 2048 interrupts but at least 64 which is double the maximum MSI interrupts.
Optional features in MSI (64-bit addressing and interrupt masking) are also mandatory with MSI-X.
- "PCI Local Bus Specification Revision 2.2". section 6.8 (MSI) (PCI-SIG). 1998.
- "PCI Local Bus Specification Revision 2.3". section 6.8 (MSI) (PCI-SIG). 2002.
- "PCI Local Bus Specification Revision 3.0". section 6.8 (MSI & MSI-X) (PCI-SIG). 2002.
- Jonathan Corbet; Greg Kroah-Hartman; Alessandro Rubini (February 2005). "Linux Device Drivers, 3rd Edition". 15.4. Direct Memory Access. O'Reilly. Retrieved 2013-10-05.
- Microsoft. "Enabling Message-Signaled Interrupts in the Registry". Microsoft Corporation. Retrieved 12 April 2013.
- "PCI Express Base Specification Revision 1.0a". section 6.1 (MSI & MSI-X) (PCI-SIG). 2003.
- "PCI Express Base Specification Revision 1.1". section 6.1 (MSI & MSI-X) (PCI-SIG). 2005.
- "PCI Local Bus Specification Revision 2.3". MSI-X Engineering Change Notice. PCI-SIG.
- MSDN paper on MSI in Windows Vista
- Introduction to Message-Signaled Interrupts - MSDN
- Linux MSI HOWTO
- Changes required to support MSI in FreeBSD (MSI / MSI-X Supported as of FreeBSD 6.3-RELEASE)
- Changes made to support MSI in Solaris Express