Skip to content

[Bebop][RushB] Decouple runtime from Verilator - #18

Open
daiyongyuan wants to merge 1 commit into
mainfrom
refactor/rushb-runtime
Open

[Bebop][RushB] Decouple runtime from Verilator#18
daiyongyuan wants to merge 1 commit into
mainfrom
refactor/rushb-runtime

Conversation

@daiyongyuan

@daiyongyuan daiyongyuan commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • base the refactor on the current topology-aware RushB implementation
  • move command, event, wait, DMA request, queueing, timeout, and shutdown types into the shared RushB crate
  • use core_id consistently; remove the obsolete accelerator/chip selection contract
  • keep Verilator-specific RTL counters, DMA staging, and simulator stepping in the Verilator backend
  • preserve mvin_mmio, Fence completion handling, per-Core routing, and single-threaded Verilator execution

This does not change the C++ FFI, RTL interface, batch regression configuration, or backend selection flow. BEMU keeps its synchronous per-Core backend because it does not expose Verilator-style Accepted/Completed events.

Verification

  • cargo test -p bebop-rushb
  • cargo clippy -p bebop-rushb --all-targets -- -D warnings
  • cargo check -p bebop-verilator with generated Toy RushB RTL
  • cargo check for the generated Toy BEMU crate
  • git diff --check

@daiyongyuan
daiyongyuan force-pushed the refactor/rushb-runtime branch from a7750a0 to 156455d Compare August 31, 2026 11:24
@daiyongyuan daiyongyuan changed the title refactor: decouple RushB runtime from Verilator [Bebop][RushB] Decouple runtime from Verilator Aug 31, 2026
@daiyongyuan
daiyongyuan force-pushed the refactor/rushb-runtime branch from 156455d to d1d8059 Compare August 31, 2026 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant