Interface Protocols · All levels

Coherence Fabric Debug: Interview Drills

Interview Drills for Coherence Fabric Debug.

Interview drills

Interview Drills for Coherence Fabric Debug focuses on deadlock signature, ordering violation count, coherency timeout rate. The goal is to connect the observable symptom to protocol mechanism, ownership, and regression risk.

diagram

PROMPT
You see deadlock signature, ordering violation count, coherency timeout rate on Coherence Fabric Debug. Walk through root cause and fix.

STRONG ANSWER
1. Names the layer and transaction identity.
2. Explains debug requires correlating transaction IDs, cache-line addresses, state transitions, and fabric backpressure.
3. Requests coherence trace, litmus replay, fabric credit graph, failing line timeline.
4. Proposes one reduced sequence and one system regression.

WEAK ANSWER
Jumps to widening the interface, increasing FIFO depth, or blaming firmware without evidence.

Diagram to draw on the whiteboard

Coherence deadlock cycle

diagram

DEADLOCK = CYCLE IN THE WAIT GRAPH

  A waits on response channel held by B
        ^                         |
        |                         v
  B waits on snoop channel held by A

Break the cycle with:
  - separate virtual channels per message class
  - guaranteed sink for responses/snoops
  - no protocol message blocked behind another class

Root-cause tree to narrate

diagram

ROOT-CAUSE TREE — Coherence Fabric Debug

deadlock signature, ordering violation count, coherency timeout rate looks wrong
        |
   reproducible?
     /        \
   no          yes
   |            |
 flaky env   same first transaction every time?
 / seed         /            \
              yes             no
               |               |
        protocol rule     timing/reset/PVT
        or config bug     or load-dependent

Protocol deep dive

Coherence extends memory transactions with snoop and state — traffic multiplies when software shares cache lines.

Concept diagram

diagram

COHERENCE TRAFFIC FLOW

RN issues coherent read
   -> HN looks up directory
   -> snoops to sharers
   -> data + state update returned

False sharing: different variables, same cache line -> coherence storm.

Metric graph

diagram

COHERENCY TRAFFIC STACK

data fetch        ████████
snoop responses   ██████████████
writebacks        ██████
maintenance ops   ████

High snoop stack with good IPC -> suspect line sharing before faster NoC.

Metrics and artifacts to collect

snoop rate
intervention latency
coherency transaction mix
false sharing indicators

Mini case study

Benchmark IPC looked fine but system power spiked: per-core counters were on one cache line. Padding counters fixed coherency traffic without any NoC change.

Debug branches

If snoop latency high, check home node placement and directory policy.
If ordering bug, run litmus sequences before microarch changes.
If traffic storm, profile cache line sharing in software layout.

Senior review question

Ask: what is the first transaction that deviates, and which spec rule does it test?

Key takeaways

Connect every protocol claim to a transaction identity and measurable metric.
Store the artifact (waveform, log, counter) next to every signoff decision.

Common pitfalls

Debugging timeouts without finding the first bad transaction.
Quoting peak bus width without payload efficiency and retry overhead.
Treating VIP compliance as a substitute for system integration replay.

Interview whiteboard

Draw layers first, then place the failing transaction on the diagram.

Practice this lesson