Home /Modules/cpu/TIMING.md

TIMING.md

lib/cpu/openrisc/TIMING.md · 25 line(s) · markdown

OpenRISC 1000 Timing

Timing events include fetch/decode, register reads, ALU/branch execution, load/store access, pipeline stalls, exceptions, interrupts, and optional extension or cache activity. Pipeline depth and instruction latency vary across implementations. Use measured or documented profile timing; leave unspecified timing unknown rather than inventing cycle counts.

Expert timing, voltages, and variable clocks (shared across all CPU models)

The per-CPU timing above is the architectural/behavioral view for this part. The adjustable, quality-first timing system is shared by every CPU model in lib/cpu and is documented once, in the package guide:

Every CPU model (this one included) inherits the clock/overclock surface from SLCPURuntime and can be assembled with those shared expert-timing, voltage, and component options; they are a build-layer concern, not re-declared per CPU.