xe_validation_should_retry(9)

💅 xe_validation_should_retry — the glazed donut of kernel API manuals

okay bestie, welcome to the xe_validation_should_retry(9) page, straight out of the Kernel API Manual ✨ this one's a tiny little function but she's lowkey important, so let's get into it 🫶

---

✨ NAME ✨

xe_validation_should_retry — literally just: determine if a validation transaction should retry 🎀

---

🌸 SYNOPSIS 🌸

bool xe_validation_should_retry (struct xe_validation_ctx *ctx , int
*ret );

that's the whole vibe, no cap 💅

---

🦋 ARGUMENTS 🦋

• ctx — the validation transaction itself. she's the main character here 👑
• ret — a pointer to a return value variable. yes queen, we're writing through a pointer 🙈

---

💖 DESCRIPTION 💖

so here's the tea ☕ this function determines whether a validation transaction should retry — and it makes that call based on the internal transaction state plus the return value pointed to by ret.

if a validation should be retried, the transaction is prepared for that, and the validation lock might be re-locked in exclusive mode, and *ret is set to 0 ✨

if the re-locking errors — typically because of interruptible locking with a signal pending — then *ret is instead set to -EINTR and the function returns false. not the slay we wanted, but okay 😭

heads up: that interruptible-locking-with-signal-pending case is the classic reason you'll get -EINTR back, so don't be surprised when it shows up, iykyk 💀

---

🔥 RETURN 🔥

true if validation should be retried, false otherwise. that's it, that's the whole answer, periodt 💅

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_validation.c — go read the source bestie, it's giving iconic
• xe_validation_assert_exec(9)
• xe_validation_ctx_init(9)
• xe_validation_exec_lock(9)
• xe_validation_ctx_fini(9)

---

and that's a wrap, bestie 🎀 this lil page lives over in ./drivers/gpu/drm/xe, dated October 2026, from the Kernel API Manual — mwah, go forth and retry responsibly 💜🦋🌸