Editing Classic RISC pipeline (section)

==Cache miss handling==

Occasionally, either the data or instruction cache does not contain a required datum or instruction.  In these cases, the CPU must suspend operation until the cache can be filled with the necessary data, and then must resume execution.  The problem of filling the cache with the required data (and potentially writing back to memory the evicted cache line) is not specific to the pipeline organization, and is not discussed here.

There are two strategies to handle the suspend/resume problem.  The first is a global stall signal.  This signal, when activated, prevents instructions from advancing down the pipeline, generally by gating off the clock to the flip-flops at the start of each stage.  The disadvantage of this strategy is that there are a large number of flip flops, so the global stall signal takes a long time to propagate. Since the machine generally has to stall in the same cycle that it identifies the condition requiring the stall, the stall signal becomes a speed-limiting critical path.

Another strategy to handle suspend/resume is to reuse the exception logic.  The machine takes an exception on the offending instruction, and all further instructions are invalidated.  When the cache has been filled with the necessary data, the instruction that caused the cache miss restarts.  To expedite data cache miss handling, the instruction can be restarted so that its access cycle happens one cycle after the data cache is filled.