SMSIC: Software-Interrupt MSI Controller for RISCV AIA in Large-Scale NoC Systems
2026-06-10 , Poster Island D

The surging demand for VM-based secure containers in the AI Agent era is driving rapid growth in the scale of vCPU deployments. However, the current RISC-V AIA specification co-locates inter-processor interrupts (IPIs) and device interrupts within the IMSIC, causing hardware resource overhead to scale multiplicatively with both the per-file size and the total count of S/VS-files — a structural coupling that fundamentally limits vCPU interrupt pass-through scalability.
To address this, we propose the Software-interrupt MSI Controller (SMSIC), an AIA extension that explicitly decouples IPI from the IMSIC external interrupt hierarchy and establishes a dedicated MSI delivery path for the software interrupts defined in the RISC-V privileged specification. By fully decoupling the IPI path from the device interrupt path, SMSIC reduces the per-VS-file IPI resource to a single interrupt entry, comprising only one enable bit and one pending bit, thereby supporting large-scale VS-file deployment at minimal hardware cost (for both the per-hart and SoC IPI merging & absorption components). Furthermore, with the IPI path isolated, IOMMU MRIF can scale the number of virtualization interrupt files to support larger-scale deployments of vCPU interrupt pass-through, effectively taking over the scalability role from native IMSIC VS-files.


In fact, mainstream architectures adopt a decoupled IPI hardware design: ARM GIC handles IPI through SGI (Software Generated Interrupt), decoupled from LPI (Locality-specific Peripheral Interrupt), which handles MSI; and the RISC-V privileged specification explicitly distinguishes Software Interrupt from External Interrupt at the architectural level, with each serving a clearly defined and non-overlapping role. However, the AIA IMSIC design appears to focus exclusively on External Interrupt, without providing an equivalent MSI delivery mechanism for Software Interrupt — leaving IPI and device interrupts tightly coupled within the IMSIC. Therefore, it is necessary to extend the AIA specification by introducing a dedicated MSI solution for Software Interrupt.

See also: SMSIC Poster (1.4 MB)

A Linux kernel developer focuses on the CPU subsystem, including virtualization, IOMMU, PCIe, Heterogeneous Programming, and RV64ILP32.

Staff Engineer, Alibaba Damo Academy

This speaker also appears in: