GSP MESSAGE HANDLING POLICY(9)

💅 GSP message handling policy(9) 💅

okay so bestie, welcome to the Kernel API Manual page for GSP message handling policy(9) — yes, the title is a mouthful, but it's lowkey iconic. This one is all about what happens when you send a GSP RPC command: there can be multiple cases of handling the GSP RPC messages, which are the reply of GSP RPC commands, according to the requirement of the callers and the nature of the GSP RPC commands. No cap, that's the whole plot. 🫶

Here's the rundown, bestie:

• NVKM_GSP_RPC_REPLY_NOWAIT — If specified, immediately return to the caller after the GSP RPC command is issued. it's giving "send it and dip" 💨
• NVKM_GSP_RPC_REPLY_NOSEQ — If specified, exactly like NOWAIT but don't emit RPC sequence number. sneaky-clean ✨
• NVKM_GSP_RPC_REPLY_RECV — If specified, wait and receive the entire GSP RPC message after the GSP RPC command is issued. patient main character energy 🧚
• NVKM_GSP_RPC_REPLY_POLL — If specified, wait for the specific reply and discard the reply before returning to the caller. look, grab the vibe, yeet the reply 💅

🌸 SEE ALSO 🌸

• Kernel file ./drivers/gpu/drm/nouveau/include/nvkm/subdev/gsp.h — that's the one, go peek 💖

mwah 💋 this page is from the Kernel API Manual, footer source/version ./drivers/gpu/drm/nouveau/incl..., dated October 2026, and titled GSP message handling policy(9). periodt. 💅🌷