tools/cuda-ab: P2 arbitrary-kernel suite expansion (regs/streams/printf), smiley push wiring, near-native perf harness (offline readiness; guest validation pending)

1 files changed, 24 insertions, 0 deletions

diff --git a/tools/cuda-ab/perf/README.md b/tools/cuda-ab/perf/README.md
new file mode 100644
index 0000000..55adceb
--- /dev/null
+++ b/tools/cuda-ab/perf/README.md
@@ -0,0 +1,24 @@
+# CUDA performance harness (perf)
+
+Near-native performance measurement for the Open-IOV emulated vGPU. One
+workload binary (`perf_workload.cu`, static CUDA runtime) runs on the host
+(bare metal, the oracle) and in the guest (emulated vGPU); `perf.sh` captures
+the matching host-side vgsp evidence and compares guest/host ratios.
+
+```
+perf.sh check     # prerequisites only (no GPU/VM action)
+perf.sh host      # oracle runs -> results/<stamp>-host/
+perf.sh guest     # push + measured runs -> results/<stamp>-guest/
+perf.sh all       # host + guest + compare
+perf.sh compare   # ratio table from the newest results
+```
+
+The full matrix, methods, thresholds, calibration procedure and evidence
+discipline are in [`PLAN-AND-HARNESS.md`](PLAN-AND-HARNESS.md). The r3
+baseline (`elapsed_ms=189`) and exactly what it measured are documented there
+in §1.
+
+Recording: raw results stay under `results/` (gitignored); the durable copy
+and the public summary go to the campaign evidence directory and
+`docs/05-operations/05-performance-results.md`, with a dated delta appended to
+`handoff-meta-plan.md` §2.