RISC-V Design ยท All levels

Privilege Levels, Execution Modes, and Delegation Boundaries: Reports and Metrics

Reports and Metrics for Privilege Levels, Execution Modes, and Delegation Boundaries.

Reports and metrics

Reports and Metrics for Privilege Levels, Execution Modes, and Delegation Boundaries is anchored on Privilege-transition latency and number of unauthorized accesses blocked by PMP/page-permission checks per billion instructions.. Convert observations into mechanism-backed decisions with explicit ownership.

Before/after trend

diagram
BEFORE / AFTER TREND - Privilege Levels, Execution Modes, and Delegation Boundaries

Privilege-transition latency and number of unauthorized accesses blocked by PMP/page-permission checks per billion instructions.
  ^
  |                           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 - Privilege Levels, Execution Modes, and Delegation Boundaries

Privilege-transition latency and number of unauthorized accesses blocked by PMP/page-permission checks per billion instructions. 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 Privilege-transition latency and number of unauthorized accesses blocked by PMP/page-permission checks per billion instructions. 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.