How wyattvo/cheri-qemu-port works
This is CHERI QEMU 10.2: a system emulator fork adding CHERI-RISC-V and Arm Morello support. The principal workflow is to start a system emulator, execute guest instructions under the selected CPU/accelerator, and interact with emulated hardware; CHERI adds capability-aware instruction behavior and extension restrictions. The README also documents TestRIG/RVFI-DII validation and CheriBSD boot support. Sampled source is mostly QEMU infrastructure rather than the CHERI target implementation, so target-specific links rely on README statements; unsampled subsystem paths are omitted where the tree gives no exact source path.
Main entry points: cpu-exec.c TCG execution · main.c System entry · dev-storage.c USB mass storage · qemu-storage-daemon.c Storage daemon
Components 15
Emulator runtime
- System entry
system/main.c - TCG execution
accel/tcg/cpu-exec.c - Translation engine
tcg/tcg.c
CHERI execution
- CHERI-RISC-V
- Arm Morello
- Unsafe extensions
Guest devices and storage
- USB mass storage
hw/usb/dev-storage.c - Storage daemon
storage-daemon/qemu-storage-daemon.c - NBD server
nbd/server.c - Reservation helper
scsi/pr-manager-helper.c
Operations and validation
- Guest agent
qga/main.c - TestRIG
- CheriBSD guest
- Morello tests
Other components
- Emulator operator
Connections 14
- Emulator operator → System entry: starts
- System entry → TCG execution: runs guest
- TCG execution → Translation engine: translates
- TCG execution → CHERI-RISC-V: executes
- TCG execution → Arm Morello: executes
- CHERI-RISC-V → Unsafe extensions: enforces policy
- Emulator operator → USB mass storage: configures device
- Emulator operator → Storage daemon: starts
storage-daemon/qemu-storage-daemon.c - Storage daemon → NBD server: serves exports
- USB mass storage → Reservation helper: uses reservations
- Emulator operator → Guest agent: starts
- TestRIG → CHERI-RISC-V: checks instructions
- CheriBSD guest → CHERI-RISC-V: boots on
- Morello tests → Arm Morello: tests execution