Lightning Talk: What in RISC-V IOPMP
summary
IOPMP defines access control for non‑RISC‑V bus masters (DMA, NICs) by mapping source IDs to memory domains (MDID) and checking permissions via a searchable entry array. The proposal specifies a row/column MDID split (higher r bits select a row, lower c bits build a column mask), row buffers of two to c entries, and an address match engine that finds matches within two to three entries and iterates per domain (not per array size). Multiple profiles (full/4‑profile, replica, compact K, isolation) trade cost, latency and throughput; remaining work covers IOPMP protection, register spec and distributed designs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:17Outline
- 0:51Why IOPMP
- 1:38Proposal
- 2:23Memory Domain
- 3:31Profiles
- 4:41Top Register
- 6:00Address Major
- 7:23Pipeline
- 8:17Profile
- 9:05Conclusion
related talks
17mEnhancing OP-TEE for RISC-V: Leveraging IOPMP and Enabling RTOS Integration
21mI/O Virtualization Use Cases and the RISC-V IOMMU Overview
23mRISC V Enclaves A Clean Slate Approach To Linux Security
13mRISC-V: Securing the Future of Open Source Computing
23mIMIX: In-Process Memory Isolation EXtension
18mIntroducing RISC-V Confidential Computing for IoT Devices
39miommufd discussion
19mOpen-Source Commercial-Grade RISC-V IOMMU with Verification
