Asymmetric Multiprocessing and Embedded Linux
summary
Asymmetric multiprocessing on SoCs uses shared memory plus interrupts with one master core managing lifecycle and one or more secondaries running RTOS or bare‑metal; Remote Processor Messaging (RPMsg) is a tiny header protocol over VirtIO vrings that enables zero‑copy via vring pointers (four rings: two per direction with alloc/free out‑of‑order). There are production components: remoteproc, RPMsg drivers, a lightweight bare‑metal stack RPMsg‑Lite + eRPC for user RPC, and working use cases for audio/video decode, power management, and radio offload.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:27Motivation - why AMP? 1/2
- 7:10RPMsg in Linux - Current State 1/2
- 21:14Library Architecture 1/2
- 27:04What is RPC?
- 30:45How to use eRPC? 2/3
related talks
27mInsights on the Re-Architecting to a Single Codebase, Running on Different Hardware...
42mInter Process Confusion - Navigating Zephyr's IPC APIs
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded...
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded De...
34mReactive Architecture
28mExploring an Architecture-neutral KVM MMU
59mSucceeding at Reactive Architecture
05mReactor vs. Proactor