kfd_process_device_init_vm(9)

💖 NAME 💖

kfd_process_device_init_vm — bestie, this is the one that sets up a VM for a process-device ✨

---

🎀 SYNOPSIS 🎀

int kfd_process_device_init_vm (struct kfd_process_device *pdd , struct
file *drm_file );

---

🦋 ARGUMENTS 🦋

• pdd — the process-device itself, the main character of this whole function 🫶
• drm_file — an optional pointer to a DRM file descriptor. Optional as in "you can pass NULL and it's still valid", not optional as in "skip it and see what happens" ngl 🙈

---

🔥 DESCRIPTION 🔥

So here's the vibe check, okay?

If drm_file is specified, it gets used to acquire the VM from that file descriptor. And the way that it works — if it succeeds, pdd takes ownership of the file descriptor. Like, full custody. Periodt. 💅

Heads up bestie: ownership transfer is real. Once it succeeds, that fd belongs to the pdd now, so don't be out here double-dipping with it 😭

If drm_file is NULL, then a brand new VM gets created instead. Fresh out of the oven, no cap ✨

And the return situation:

• Returns 0 on success 🎉
• Returns -errno on failure 💀

That's literally it, but it's iconic 💜

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/amd/amdkfd/kfd_process.c
• kfd_get_cu_occupancy(9)
• amdgpu_amdkfd_set_sigbus_delay(9)

---

okay that's the whole page bestie, go forth and init those VMs 🧚

this masterpiece lives over in ./drivers/gpu/drm/amd/amdkfd, dated October 2026, and it's literally called kfd_process_device_init_vm(9) in case you forgot on your way down here 💖