RISC-V Design · All levels

RISC-V Design Cheatsheet

Dense reference for mechanism-first debugging and architecture closure decisions.

Debug order

diagram
WORKLOAD -> MECHANISM -> ARTIFACT -> OWNER -> DECISION

DECODE: legality, control bundles, critical fanout
PIPELINE: forwarding, hazards, flush/redirect races
PRIVILEGE: trap sequencing, CSR legality, delegation
MEMORY: TLB/walk behavior, sfence discipline, protection checks
EXTENSIONS: profile compatibility, fallback correctness, throughput impact
SIGNOFF: regression matrix, risk ownership, rollback gates

Questions before proposing a fix

  1. Which workload fails first and how reproducible is it?

  2. Which mechanism path fails first under locked metadata?

  3. Which artifact proves causality?

  4. Who owns the smallest reversible fix?

  5. What validation and rollback gates close release risk?