Instruction step loop + per-step peripheral tick
Priority 0 - Core Emulator Infrastructure / 0.1 Execution core: time, scheduling, determinism
As an emulator integrator, I want vemu's Instruction step loop + per-step peripheral tick to stay accurate, tested, and documented, so that I can keep depending on the actual execution engine.
Why it matters
The actual execution engine
Summary
Drives the machine: step CPU - > tick peripherals - > dispatch IRQs
Scope of work
Already implemented. Harden, broaden coverage, add tests and documentation for Instruction step loop + per-step peripheral tick. What it is: Drives the machine: step CPU - > tick peripherals - > dispatch IRQs. Why it matters: The actual execution engine.
Current state
Status: Fully implemented. Notes / evidence: vemu-cortex-m/src/machine.rs, vemu-cortex-a/src/machine_a53_64.rs - polling, not event-driven.
Unblocks 17
Funding this also clears the way for the work below.
- Done
- Done
Activity log
Feature defined and added to the roadmap
Funding goal set to $2,250
Implementation status: Implemented
Delivered - counted as fully funded