RISC-V Design · All levels
Coverage-Driven Verification: Reports and Metrics
Reports and Metrics for Coverage-Driven Verification.
Reports and metrics
Reports and Metrics for Coverage-Driven Verification is anchored on Risk-weighted closure across functional coverage, assertion coverage, code coverage, and bug escape trend.. Convert observations into mechanism-backed decisions with explicit ownership.
Before/after trend
diagram
BEFORE / AFTER TREND - Coverage-Driven Verification
Risk-weighted closure across functional coverage, assertion coverage, code coverage, and bug escape trend.
^
| o target band
| o after fix + reruns
| o
| o baseline (failing)
+--------------------------------------------------> iteration
capture issue isolate mechanism close + monitor
Use this view to confirm the gain is causal and stable across seeds.Root-cause tree
diagram
ROOT CAUSE TREE - Coverage-Driven Verification
Risk-weighted closure across functional coverage, assertion coverage, code coverage, and bug escape trend. regressed
|
reproducible on fixed seed?
/ \
no yes
| |
env/tool drift first failing domain?
/ | \
decode execute memory/MMU
| | |
control map bypass/FU TLB/walk/perm
|
privilege/CSR side effects checked?
Stop at first confirmed mechanism, then assign explicit owner + fix proof.Track Risk-weighted closure across functional coverage, assertion coverage, code coverage, and bug escape trend. on representative workloads, not just microbenchmarks.
Include build/runtime/privilege metadata in report headers.
Pair performance movement with correctness and reliability checks.
Report tail stability, not only mean uplift.