Home /Modules/cpu/TIMING.md

TIMING.md

lib/cpu/system-360/TIMING.md · 42 line(s) · markdown

System/360 Timing and Performance

Model-specific timing

There is no single cycle count or execution rate for the System/360 family. Timing depends on the machine model, instruction, operand location, installed options, storage technology, channel activity, and system load.

Evidence labels

Performance dimensions

Track instruction execution, storage waits, channel activity, interruption overhead, and device waits separately. Do not include unmodeled operating-system or I/O time as intrinsic CPU latency.

Reports

Identify the machine model, options, storage configuration, and evidence class. Do not present estimates as guaranteed timing.

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.