radeon_vm_u...ge_directory(9)

📦 version 7.3.1, in nixpkgs unstable

💖 radeon_vm_update_page_directory(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ this one's from the <./drivers/gpu/drm/radeon> girlies and it's literally the page-directory glow-up function, iykyk 🦋

🌸 NAME 🌸

radeon_vm_update_page_directory — make sure that page directory is valid 💅 no cap, that's the whole job

✨ SYNOPSIS ✨

int radeon_vm_update_page_directory (struct radeon_device *rdev , struct
radeon_vm *vm );

like, it takes two things and returns an int, periodt 🎀

🫶 ARGUMENTS 🫶

  • rdev — a radeon_device pointer 👑 your device, the main character
  • vm — the requested vm 🧚 the virtual memory vibes you're asking about

💫 DESCRIPTION 💫

So what it does: it allocates new page tables if necessary and then updates the page directory — and heads up, that's (cayman+) only, so older chips can sit this one out 🙈

It returns 0 for success and an error for failure, fr fr 😭 no in-between.

⚠️ ok this is the important part: Global and local mutex must be locked! both of them. locked. before you call this. not a suggestion, bestie, it's giving "do it or things go very bad" 💀🔒

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/radeon/radeon_vm.c — go read it, it's iconic 👑

and then the whole friend group, literally the entire squad 🫶:

and that's the whole page, bestie 🍓 this little cutie lives in ./drivers/gpu/drm/radeon, it's dated October 2026, and the header says radeon_vm_u...ge_directory(9) — yes the title's truncated, that's just how it ate 😭💖 mwah, go lock those mutexes 🎀✨

📦 where this page comes from