gpu_buddy_driver_set_lock(9)

💅 gpu_buddy_driver_set_lock 💅

okay bestie, so this is a kernel API manual page for gpu_buddy_driver_set_lock(9) — yes that's the function and the man page section, we love a name that does both 🎀

---

✨ NAME ✨

gpu_buddy_driver_set_lock — sets the lock that protects accesses to GPU BUDDY 🔒🦋

🌸 SYNOPSIS 🌸

gpu_buddy_driver_set_lock (mm , lock );

like, that's the whole call, no cap ✨

🧚 ARGUMENTS 🧚

• mm — pointer to the GPU buddy structure. yes it's called mm, no we're not gonna question it 💀
• lock — the lock used to protect the gpu buddy. important: the locking primitive must contain a dep_map field. that's not a suggestion, that's the vibe check, and if your lock fails it, bestie, it fails 😭

👑 DESCRIPTION 👑

Call this to annotate gpu_buddy APIs which access/modify the gpu_buddy manager 🫶

that's literally it — it's an annotation situation, the main character move that tells everyone which lock is guarding the gpu_buddy manager 💅✨

🌈 SEE ALSO 🌈

Kernel file ./include/linux/gpu_buddy.h, plus the whole squad:

• GPU_BUDDY_RANGE_ALLOCATION(9)
• GPU_BUDDY_TOPDOWN_ALLOCATION(9)
• GPU_BUDDY_CONTIGUOUS_ALLOCATION(9)
• GPU_BUDDY_CLEAR_ALLOCATION(9)
• GPU_BUDDY_CLEARED(9)
• GPU_BUDDY_TRIM_DISABLE(9)
• struct gpu_buddy_block(9)
• struct gpu_buddy(9)
• gpu_buddy_driver_lock_held(9)

go read gpu_buddy_driver_lock_held(9) next, it's giving sequel energy 👀🔥

---

sign-off time 🎀 this one lives in ./include/linux, dated October 2026 — so yeah, future vibes, screenshot it and study later iykyk 💜🦋⭐