xe_pm_block_on_suspend(9)

📦 version 7.3.1, in nixpkgs unstable

💖 xe_pm_block_on_suspend(9) 💖

okay so real talk, this is a page from the Kernel API Manual and it's all about xe_pm_block_on_suspend — one tiny little function with big "don't talk to me while I'm getting ready" energy. bestie, let's get into it 🎀

✨ NAME ✨

xe_pm_block_on_suspend — block pending suspend. that's it. that's the whole vibe. 💅

🌸 SYNOPSIS 🌸

int xe_pm_block_on_suspend (struct xe_device *xe );

literally one function, one argument, one int coming back at ya. iconic. ✨

🦋 ARGUMENTS 🦋

  • xe — the xe device that's about to be suspended. like, the main character of this whole situation.

💜 DESCRIPTION 💜

so here's the tea 🍵 — this function blocks if the pm notifier has started evicting bos, and the whole point is to avoid racing and validating those bos back. no cap, that's the reason. 😭

the function is annotated to make sure you're not holding any locks that are also grabbed in the pm notifier or in the device suspend / resume. so like... don't be that girl holding a lock she shouldn't. 🙈

this is intended to be used by freezable tasks only — not freezable workqueues, i'm begging you. the intention is that the function returns -ERESTARTSYS when tasks are frozen during suspend, which lets the task go ahead and freeze. 🧊

⚠️ heads up bestie: the caller must be able to handle the -ERESTARTSYS. if your caller can't handle it, do not pass go, do not collect $200. 💀

👑 RETURN 👑

  • 0 — on success, slay ✨
  • -ERESTARTSYS — on signal pending, or if freezing was requested 🥶

🌈 SEE ALSO 🌈

okay this list is long and honestly it ate. here's the whole squad, and also where to find the kernel file:

kernel file ./drivers/gpu/drm/xe/xe_pm.c — Xe Power Management(9), plus:

that's the whole page, bestie. no crumbs left. 🫶

so yeah — this lives in ./drivers/gpu/drm/xe, dated October 2026, and it's xe_pm_block_on_suspend(9) through and through. go block that suspend responsibly, mwah 💋 periodt 🌈⭐

📦 where this page comes from