Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH i-g-t v2] tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures
@ 2026-05-06  9:14 Karthik B S
  2026-05-06 13:52 ` ✗ i915.CI.BAT: failure for tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures (rev2) Patchwork
                   ` (6 more replies)
  0 siblings, 7 replies; 9+ messages in thread
From: Karthik B S @ 2026-05-06  9:14 UTC (permalink / raw)
  To: igt-dev; +Cc: pranay.samala, Karthik B S, S Sebinraj, Krzysztof Karas

Track per-plane timeline/fence state across the in-flight NONBLOCK atomic
commit and install an exit handler to signal any still-unsignaled fences.
This prevents cleanup hangs when an assertion fires after commit
submission but before the test signals the blocking fence.

V2:
 - Drop the redundant 'active' variable
 - Reset timelines[i] to -1 in signal_pending_fences()

Cc: S Sebinraj <s.sebinraj@intel.com>
Cc: Krzysztof Karas <krzysztof.karas@intel.com>
Signed-off-by: Karthik B S <karthik.b.s@intel.com>
Reviewed-by: S Sebinraj <s.sebinraj@intel.com>
---
 tests/kms_explicit_fence.c | 44 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)

diff --git a/tests/kms_explicit_fence.c b/tests/kms_explicit_fence.c
index 2ec9bf39d..930f5a970 100644
--- a/tests/kms_explicit_fence.c
+++ b/tests/kms_explicit_fence.c
@@ -68,6 +68,38 @@ typedef struct {
 	igt_pipe_crc_t *pipe_crc;
 } data_t;
 
+/*
+ * State tracked across the lifetime of an in-flight atomic commit that has
+ * IN_FENCEs attached. The exit handler uses this to unblock any pending
+ * commit if an assert hits between the commit and the point where
+ * the test would otherwise signal the unsignaled fence(s).
+ */
+static struct {
+	int timelines[NUM_PLANES];
+	bool needs_signal[NUM_PLANES];
+} pending_fence_state = {
+	.timelines = { -1, -1, -1 },
+};
+
+static void signal_pending_fences(int sig)
+{
+	for (int i = 0; i < NUM_PLANES; i++) {
+		if (pending_fence_state.timelines[i] < 0)
+			continue;
+
+		if (pending_fence_state.needs_signal[i]) {
+			/*
+			 * Best-effort: advance the timeline so the kernel
+			 * stops waiting on this IN_FENCE.
+			 */
+			sw_sync_timeline_inc(pending_fence_state.timelines[i], 1);
+			pending_fence_state.needs_signal[i] = false;
+		}
+
+		pending_fence_state.timelines[i] = -1;
+	}
+}
+
 static void setup_output(data_t *data)
 {
 	igt_display_t *display = &data->display;
@@ -242,6 +274,9 @@ static void multiplane_atomic_fence_wait(data_t *data)
 
 		/* Attach IN_FENCE_FD to plane */
 		igt_plane_set_fence_fd(planes[i], fences[i]);
+
+		pending_fence_state.timelines[i] = timelines[i];
+		pending_fence_state.needs_signal[i] = !should_signal[i];
 	}
 
 	/* Swap overlay colors to detect scanout changes via CRC */
@@ -299,6 +334,7 @@ static void multiplane_atomic_fence_wait(data_t *data)
 	igt_assert_crc_equal(&crc_before, &crc_after);
 
 	/* Now signal the blocking fence (overlay2) */
+	pending_fence_state.needs_signal[PLANE_OVERLAY2_IDX] = false;
 	sw_sync_timeline_inc(timelines[PLANE_OVERLAY2_IDX], 1);
 
 	/* Wait for overlay2 fence to be signaled */
@@ -353,6 +389,13 @@ int igt_main()
 
 		data.pipe_crc = igt_pipe_crc_new(data.drm_fd, data.crtc->crtc_index,
 						 IGT_PIPE_CRC_SOURCE_AUTO);
+
+		/*
+		 * Make sure that on a failure mid-test, any unsignalled
+		 * IN_FENCE that the kernel is still waiting on gets
+		 * signaled so cleanup can complete instead of hanging.
+		 */
+		igt_install_exit_handler(signal_pending_fences);
 	}
 
 	igt_describe("Test atomic commit with 3 planes (1 primary, 2 overlay) "
@@ -363,6 +406,7 @@ int igt_main()
 		multiplane_atomic_fence_wait(&data);
 
 	igt_fixture() {
+		signal_pending_fences(0);
 		reset_display_state(&data);
 		igt_pipe_crc_free(data.pipe_crc);
 		cleanup_crtc(&data);
-- 
2.43.0


^ permalink raw reply related	[flat|nested] 9+ messages in thread
end of thread, other threads:[~2026-05-11  4:31 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-06  9:14 [PATCH i-g-t v2] tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures Karthik B S
2026-05-06 13:52 ` ✗ i915.CI.BAT: failure for tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures (rev2) Patchwork
2026-05-06 13:54 ` ✓ Xe.CI.BAT: success " Patchwork
2026-05-06 15:15 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-07  6:02 ` [PATCH i-g-t v2] tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures Krzysztof Karas
2026-05-08  4:39 ` ✓ i915.CI.BAT: success for tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures (rev2) Patchwork
2026-05-08 23:20 ` ✗ i915.CI.Full: failure " Patchwork
2026-05-11  4:30   ` Karthik B S
2026-05-11  3:40 ` [PATCH i-g-t v2] tests/kms_explicit_fence: Rescue pending IN_FENCE waits on test failures Samala, Pranay

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox