Instruction Issue & Scoreboard: Debug Playbook

Debug playbook

Debug Playbook for Instruction Issue & Scoreboard centers on issue slot utilization, dependency stall ratio, and scoreboard wait depth. The objective is to connect profiler evidence to root-cause mechanism and release-safe action.

GPU debug is mechanism-first. Lock revisions, isolate first failing workload, then prove one hypothesis before applying broad tuning.

Root-cause tree

ROOT-CAUSE TREE — Instruction Issue & Scoreboard

issue slot utilization, dependency stall ratio, and scoreboard wait depth regressed
        |
  reproducible on replay?
      /              \
    no                yes
    |                  |
env/test noise    counter triage
                   |
             compute-bound or memory-bound?
                /                  \
             compute            memory/interconnect
             issue stalls       cache/NoC/DRAM stalls

Stop at first failing mechanism, then patch.

1. Freeze workload seed, compiler, driver, firmware, and hardware tags.

2. Identify first failing metric and where it appears in timeline.

3. Classify bottleneck domain: scheduler, execution, memory, interconnect, or thermal.

4. Build one focused reproducer that isolates dominant mechanism.

5. Patch smallest owner-controlled fix.

6. Re-run quality, performance, and stability matrix.

Review memo template

GPU DESIGN REVIEW MEMO - Shader Multiprocessor & Core Pipeline / Instruction Issue & Scoreboard

1. Symptom
   - Watched metric: issue slot utilization, dependency stall ratio, and scoreboard wait depth
   - Failing workload or scene: <name>
   - Impacted stage: <warp scheduling, memory hierarchy, graphics stage, interconnect>
   - Revision tags: <kernel/driver/compiler/firmware/hardware>

2. Mechanism hypothesis
   - Primary mechanism: Scoreboards track data hazards and memory readiness so schedulers issue only safe instructions; scoreboard pressure directly limits ILP extraction.
   - Competing hypotheses: <divergence, memory coalescing, scheduling, thermal throttling>
   - Missing evidence: <counter capture, trace, topology heatmap, timing report>

3. Proposed action
   - Minimal reversible change: <kernel/config/RTL/policy update>
   - Expected movement: <throughput, frame-time tail, perf-per-watt>
   - Regression risk: scheduler fairness, cache contention, thermal behavior, software compatibility

4. Signoff
   - Re-run artifact: scoreboard state timeline, issue reason breakdown, and stall attribution report
   - Required owners: SM RTL owner, verification owner, performance lead
   - Final decision: ship, bounded rollout, rollback, or escalate

GPU deep dive

Shader-core throughput is gated by issue policy, register-bank access, and pipeline hazard behavior.

Concept diagram

SM CORE LOOP

warp schedulers -> issue ports -> ALU/FPU/Tensor pipelines
scoreboard + register file gate progress

Metric graph

SM BOTTLENECK MIX

dependency stalls   ███████
bank conflicts      ████
pipeline bubbles    ███

Reports and artifacts

• SM IPC dashboard

• issue stall taxonomy

• register-bank conflict log

• shader unit utilization

Mini case study

Compiler register allocation shifted operand banking, doubling RF conflicts and causing a 14% shader regression.

Debug branches

• Inspect scoreboard wait-depth trends

• Track RF conflicts by instruction class

• Separate front-end issue loss from backend saturation

Senior review question

Ask: which metric and benchmark pairing proves this topic is truly closed in production context?

Key takeaways

• Always pair micro-kernel metrics with end-to-end workload impact.

• Lock toolchain, driver, and launch metadata before comparing performance results.

Common pitfalls

• Optimizing occupancy without checking memory-system saturation.

• Comparing profiler captures from different driver or compiler builds.

• Declaring wins without reproducible accuracy and performance gates.

Principal GPU review addendum

Instruction Issue & Scoreboard is not just a definition to memorize. In a real GPU program it becomes an interaction between software shape, compiler mapping, warp execution, memory movement, interconnect policy, and physical limits. The first senior move is to name which layer is being exercised before interpreting a counter.

Scoreboards track data hazards and memory readiness so schedulers issue only safe instructions; scoreboard pressure directly limits ILP extraction. This mechanism matters because GPUs are throughput machines: a small inefficiency repeated across lanes, warps, SMs, frames, or dispatches can dominate product performance even when a unit-level diagram looks balanced.

Use issue slot utilization, dependency stall ratio, and scoreboard wait depth as an entry point, not as the conclusion. A metric shift only becomes actionable after it is tied to a workload slice, a profiler capture, an architectural path, and a reproducible artifact such as scoreboard state timeline, issue reason breakdown, and stall attribution report.

SM microarchitecture efficiency is set by datapath balance, issue policy, and operand delivery. The review posture is therefore evidence-first: explain what the kernel or graphics workload asked for, how the GPU mapped it onto hardware, where useful work stopped, and which owner can change the smallest boundary safely.

In review, insist on a concrete chain from workload to hardware behavior: workload shape -> compiler/runtime mapping -> warp or pipeline behavior -> memory/fabric pressure -> measured product impact. That chain prevents generic GPU tuning advice from replacing engineering evidence.