vgsp: fail4 r233 - budgeted REC-DUMP + READ-DIVERGE-WIT (fill vs copy-path vs ledger)

r231/r232: the probe-class launches produced zero REC-DUMP lines while the
transformer's 8+2 appeared - the per-line pr_info_ratelimited was
suppressed wholesale during the probe's post-stall logging burst. REC-DUMP
now uses plain pr_info under a boot-wide 512-line budget, so a <=64-rec
launch always dumps its full rec table.

READ-DIVERGE-WIT (sema service, rec-build loop): for small launches the
three resolutions of each VA are compared side by side - the fill's
dg->pa (the page whose content the copy-in stages; exactly what the engine
reads), svc_op_translate (the H2D/D2H copy path's resolver) and the
ledger's write landing. A page-level split is logged with op_src/op_rc and
an op-miss token. Bounded: first 8 recs, boot budget 128.

Static permutation check (negative): reloc_va is assigned sequentially in
fill order (svc_gr_data_fill), copy-in/out iterate recs in order, the
engine reads reloc-base + linear offset, and the per-page copy loop folds
in-page offsets correctly on every resolver path; no sort/rotate/LIFO
order found in the page-table or copy paths. The remaining split suspect is
the m171/m180 ledger DIVERGE preference - exactly what READ-DIVERGE-WIT
compares.

Build green.

(cherry picked from commit 59e50207d60067b5d1e3a0546f20e9b22c92e112)

1 files changed, 13 insertions, 5 deletions

diff --git a/kernel/gsp_phys_booter.c b/kernel/gsp_phys_booter.c
index 7b6a1bf..430b518 100644
--- a/kernel/gsp_phys_booter.c
+++ b/kernel/gsp_phys_booter.c
@@ -165,6 +165,7 @@ static u64 gsp_phys_gr_outwit_va[GSP_PHYS_GR_OUTWIT_SLOTS];
 static u32 gsp_phys_gr_outwit_bi[GSP_PHYS_GR_OUTWIT_SLOTS];
 static u32 gsp_phys_gr_outwit_n;
 static u32 gsp_phys_gr_alias_log;	/* boot-wide alias-line budget */
+static u32 gsp_phys_gr_recdump_budget;	/* r233 REC-DUMP boot budget */
 
 bool gsp_phys_boot_enabled(void)
 {
@@ -18733,18 +18734,25 @@ int gsp_phys_backend_guest_gr_submit(const struct gsp_phys_gr_submit *req,
 	 * HPAs against the buffer the client actually uploaded (distinct
 	 * VAs collapsing onto one HPA, or HPAs in a foreign range, are
 	 * visible directly). Big launches log the first/last 8 recs only.
+	 * r233: plain pr_info with a boot-wide line budget - the earlier
+	 * pr_info_ratelimited version was suppressed wholesale during the
+	 * probe's post-stall logging burst, so the probe-class recs never
+	 * reached the ring.
 	 */
-	if (gsp_phys_gr_copywit_enabled() && req->n_data) {
+	if (gsp_phys_gr_copywit_enabled() && req->n_data &&
+	    gsp_phys_gr_recdump_budget < 512u) {
 		u32 d;
 
 		for (d = 0; d < req->n_data; d++) {
 			if (req->n_data > 64u && d >= 8u &&
 			    d < req->n_data - 8u)
 				continue;
-			pr_info_ratelimited("vgsp-gr: REC-DUMP[%u/%u] va=0x%llx hpa=0x%llx reloc=0x%llx\n",
-					    d, req->n_data, req->data[d].va,
-					    req->data[d].hpa,
-					    req->data[d].reloc_va);
+			if (gsp_phys_gr_recdump_budget >= 512u)
+				break;
+			gsp_phys_gr_recdump_budget++;
+			pr_info("vgsp-gr: REC-DUMP[%u/%u] va=0x%llx hpa=0x%llx reloc=0x%llx\n",
+				d, req->n_data, req->data[d].va,
+				req->data[d].hpa, req->data[d].reloc_va);
 		}
 	}