Skip to content
STIMSMITH

Completion Queue

Concept

In the e500 processor pipeline, the Completion Queue sits after the Completion stage and before the Write-back stage, holding in-flight instructions so the core can enforce in-order completion despite out-of-order execution.

First seen 7/3/2026
Last seen 7/3/2026
Evidence 2 chunks
Wiki v1

WIKI

Completion Queue

The Completion Queue is a micro-architectural structure in the pipeline of the e500 processor, a core based on Power Architecture Technology. It appears in the published instruction pipeline flow as the rightmost functional block, receiving instructions from the Completion stage and feeding them into the Write-back stage.

Position in the e500 pipeline

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

1 connections
e500 processor part of → 95% 2e
The e500 processor contains a completion queue

CITATIONS

4 sources
4 citations — click to collapse
[1] The Completion Queue is a pipeline stage of the e500 processor, placed after the Completion stage and before the Write-back stage. Directed Micro-architectural Test Generation for an Industrial Processor: A Case Study
[2] The e500 processor supports out-of-order execution and in-order completion for dynamic scheduling, a behavior enabled by the Completion Queue. Directed Micro-architectural Test Generation for an Industrial Processor: A Case Study
[3] The Completion Queue has finite capacity that upstream stages (such as decode) must respect, motivating directed test cases such as checking that decode is stalled when the Completion Queue is full. Directed Micro-architectural Test Generation for an Industrial Processor: A Case Study
[4] The processor model is partitioned along the functional units shown in the pipeline diagram (including the Completion Queue) for verification and directed test generation via decompositional model checking. Directed Micro-architectural Test Generation for an Industrial Processor: A Case Study