xe_exec_queue_get_lrc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ xe_exec_queue_get_lrc(9) β€” like, the Kernel API Manual page for getting your LRC ✨

okay so bestie, welcome to xe_exec_queue_get_lrc(9), straight out of the Kernel API Manual. it's a lil one but she's iconic, and I'm gonna walk you through it πŸ’…


🌸 NAME 🌸

xe_exec_queue_get_lrc β€” bestie, it gets the LRC from the exec queue. that's the whole vibe. no cap.


✨ SYNOPSIS ✨

struct xe_lrc * xe_exec_queue_get_lrc (struct xe_exec_queue *q , u16 idx );

like, literally exactly that. copy it character for character or don't come for me πŸ™ˆ


πŸŽ€ ARGUMENTS πŸŽ€

  • q β€” the exec queue instance. she's the main character here πŸ‘‘
  • idx β€” the index within the multi-LRC array. yes, you gotta tell her which one πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

So what she does is: retrieves the LRC of the given index for the exec queue β€” under lock, bestie β€” and takes a reference. the way she's out here locking AND referencing?? obsessed. she's doing the absolute most and we love her for it πŸ”₯


⭐ RETURN ⭐

  • a pointer to the LRC on success πŸŽ‰
  • an error on failure 😭
  • NULL on lookup failure πŸ’€

three possible outcomes, she keeps you guessing fr fr


🌈 SEE ALSO 🌈

okay this list is LONG, so buckle up buttercup, every single one of these is getting its moment:

go read all of them. i'll wait 🫢


ngl bestie, one tiny note β€” the "under lock and takes reference" thing in DESCRIPTION means the locking and the ref-taking are part of the package. don't go thinking you can skip out on either one, she's not that kind of function πŸ’€

and that's a wrap on xe_exec_queue_get_lrc(9)!! 🧚 she lives in ./drivers/gpu/drm/xe and this lil gem is dated October 2026 β€” periodt, that's the source, the version, and the date all in one cute lil sign-off πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from