summaryrefslogtreecommitdiffstats
path: root/kernel/gsp_phys_booter.c
diff options
context:
space:
mode:
Diffstat (limited to 'kernel/gsp_phys_booter.c')
-rw-r--r--kernel/gsp_phys_booter.c17
1 files changed, 17 insertions, 0 deletions
diff --git a/kernel/gsp_phys_booter.c b/kernel/gsp_phys_booter.c
index 10d40c6..0072fe1 100644
--- a/kernel/gsp_phys_booter.c
+++ b/kernel/gsp_phys_booter.c
@@ -18869,6 +18869,23 @@ bool gsp_phys_gr_mme_carry_peek(u32 *h_object)
}
/*
+ * Is the carrier's channel context still alive for a self-candidate launch?
+ *
+ * CONT 546: the armed carrier normally waits for a matching CLIENT beef
+ * candidate in the pump pass; when the guest's 2-frame mission ends before
+ * one re-appears (c880: ARM gen=3, no FIRE/CANCEL/WAIT), the carrier
+ * expired silently. The pump may instead submit the carrier as its own
+ * synthetic candidate when the channel's golden pack is still contiguously
+ * loaded there. This probe is that gate: the pack load handle must still be
+ * the carrier's channel (a gone context is then reported, never silent).
+ */
+bool gsp_phys_gr_mme_carry_ctx_alive(u32 h_object)
+{
+ return READ_ONCE(gsp_phys_gr_mme_pack_load_h) == h_object &&
+ gsp_phys_gr_golden_ready();
+}
+
+/*
* Claim the armed carrier for one launch. The live state is re-validated
* here, not at arm time: the pack must still be partial for this channel,
* still loaded contiguously from word 0 on it, and the golden overlay must