OpenAMP Libmetal Shared Memory Cross OS Interface
summary
OpenAMP extends by adding a libmetal-backed shared memory API and a Linux backend that aims for zero copy large‑data transfer instead of current rpmsg limits like 16‑bit rpmsg length. Design uses DMA‑BUF via ION to allocate/export device addresses, a proposed remoteproc API to import DMA-BUF and standard dma_ops for sync, and new libmetal calls libmetal share_map/attach/sync. Work is exploratory: prototypes and kernel hooks exist but full integration and kernel-to-remoteproc device linkage remain unresolved.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:45IP Message
- 4:27Use Cases
- 4:51App Message Copying
- 7:31Large Data Sharing
- 10:06Memory System
- 11:16tardiness implementation
- 12:51allocation implementation
- 17:20iommu
- 20:42kernel
- 22:42discussion
related talks
29mIntroduction to OpenAMP
22mEnhancing OpenAMP: Making Linux and Zephyr Work Better Together- 22mEnhancing OpenAMP: Making Linux and Zephyr Work Better Together
20mEnabling the Full Power of a Multiprocessor SoC
39mSoftware Defined Hardware on Heterogeneous SoCs Using OpenAMP
39mAsymmetric/Heterogeneous MultiProcessing (AMP/HMP): Mainline Linux and Zephyr in Unison
37mBuilding a Zero-Copy DSP Offload Framework in Linux Using RPM...
37mEnabling Multi-image Applications with AMP Support on ESP32