xe_pxp_get_readiness_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_pxp_get_readiness_status πŸ’…

okay bestie, welcome to the xe_pxp_get_readiness_status(9) page β€” yep, that's the Kernel API Manual, and yes it's a whole vibe 🫢 this lil function is literally the bouncer at the club checking if PXP is ready for userspace to come in ✨


🌸 NAME 🌸

xe_pxp_get_readiness_status β€” check whether PXP is ready for userspace use πŸ’–

like, is it ready or is it not ready, that is the question πŸŽ€


✨ SYNOPSIS ✨

int xe_pxp_get_readiness_status (struct xe_pxp *pxp );

no cap, that's the whole signature πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pxp β€” the xe_pxp pointer. and yes bestie, it can be NULL if PXP is disabled πŸ™ˆ pls note that, it's giving "optional but make it safe"

πŸ”₯ RETURN πŸ”₯

okay so the return values are the main character here, pay attention πŸ‘€

  • 0 β€” PXP is not ready yet 😭 like it's still getting ready, give it a sec
  • 1 β€” PXP is ready πŸŽ‰ slay, we're so back
  • a negative errno value β€” PXP is not supported/enabled, or something went wrong while initializing the prerequisites πŸ’€ not the prerequisites failing
and the important footnote bestie: these return values follow the uapi (see drm_xe_query_pxp_status), so they can be used directly in the query ioctl 🫢 no extra translation layer needed, we love a consistent icon

🌈 SEE ALSO 🌈

like, read the whole friend group tbh, they're all connected πŸ§šπŸ’œ


aaaand that's the page!! mwah πŸ’‹ this icon lives in ./drivers/gpu/drm/xe, dated October 2026, and it's literally xe_pxp_get_readiness_status(9) β€” periodt πŸ’…βœ¨

πŸ“¦ where this page comes from