xe_pxp_bo_key_check(9)

💅 xe_pxp_bo_key_check(9) 💅

okay so this is a page from the Kernel API Manual bestie, and it's literally about one tiny function that does a vibe check on your BO's key 🔑✨

---

✨ NAME ✨

xe_pxp_bo_key_check — bestie, this is the function that checks whether the key some xe_bo is using is actually valid 🎀

---

🌸 SYNOPSIS 🌸

int xe_pxp_bo_key_check (struct xe_pxp *pxp , struct xe_bo *bo );

like that's it. that's the whole signature. two args, one int back, no cap 🫶

---

🦋 ARGUMENTS 🦋

• pxp — the xe->pxp pointer, and heads up, it will literally be NULL if PXP is disabled. not "maybe", not "possibly" — it will be NULL. iykyk 💀
• bo — the BO we want to check. that's the one. the main character 🎀

---

💖 DESCRIPTION 💖

so what it does is: it checks whether a BO was encrypted with the current key or with an obsolete one. that's the whole bit. key audit energy, honestly iconic 👑

---

🔥 RETURN 🔥

it gives you back an int, and the value tells you everything:

• 0 → slay, the key is valid ✅
• -ENODEV → PXP is disabled, so like… nothing to check here bestie 🙈
• -EINVAL → the BO is not using PXP at all, so this whole call was not it 😭
• -ENOEXEC → nope, the key is not valid. failed the vibe check, periodt 💀

---

🌈 SEE ALSO 🌈

kernel file ./drivers/gpu/drm/xe/xe_pxp.c, plus the whole PXP friend group 🫶:

• PXP(9)
• xe_pxp_get_readiness_status(9)
• xe_pxp_irq_handler(9)
• xe_pxp_init(9)
• xe_pxp_exec_queue_set_type(9)
• xe_pxp_exec_queue_add(9)
• xe_pxp_exec_queue_remove(9)
• xe_pxp_key_assign(9)
• xe_pxp_obj_key_check(9)
• xe_pxp_pm_suspend(9)
• xe_pxp_pm_resume(9)

---

aaaand that's the page!! 💜 this lil gem lives in ./drivers/gpu/drm/xe, it's dated October 2026, and the whole thing is filed under xe_pxp_bo_key_check(9) — go forth and check those keys bestie, ily, mwah 🧚💖