radeon_vm_frag_ptes(9)

💖 radeon_vm_frag_ptes(9) 💖

This is radeon_vm_frag_ptes(9), straight out of the Kernel API Manual. Bestie, we're getting into fragment info for PTEs and it's gonna be cute and correct, okay? 🎀

🎀 NAME 🎀

radeon_vm_frag_ptes — add fragment information to PTEs. That's the whole name section, no cap. ✨

✨ SYNOPSIS ✨

Okay so the signature is giving exactly this, bestie:

void radeon_vm_frag_ptes (struct radeon_device *rdev , struct radeon_ib *ib , uint64_t pe_start , uint64_t pe_end , uint64_t addr , uint32_t flags );

💅 ARGUMENTS 💅

• rdev — a radeon_device pointer. The device itself, basically.
• ib — the IB for the update. 💫
• pe_start — first PTE to handle.
• pe_end — last PTE to handle.
• addr — the addr those PTEs should point to. Yes, addr points to an addr, iykyk. 😌
• flags — hw mapping flags.

🌸 DESCRIPTION 🌸

🚨 Global and local mutex must be locked! 🚨

That's it. That's the description. No extra lore, no secret bonus paragraph — just the very important locked-mutex vibe check. Both the global and local mutex, bestie. Don't skip it. 😭🔒

🦋 SEE ALSO 🦋

Kernel file ./drivers/gpu/drm/radeon/radeon_vm.c is right there in the group chat, and the whole squad is listed:

• radeon_vm_num_pdes(9)
• radeon_vm_directory_size(9)
• radeon_vm_manager_init(9)
• radeon_vm_manager_fini(9)
• radeon_vm_get_bos(9)
• radeon_vm_grab_id(9)
• radeon_vm_flush(9)
• radeon_vm_fence(9)
• radeon_vm_bo_find(9)
• radeon_vm_bo_add(9)
• radeon_vm_set_pages(9)
• radeon_vm_clear_bo(9)
• radeon_vm_bo_set_addr(9)
• radeon_vm_map_gart(9)
• radeon_vm_page_flags(9)
• radeon_vm_update_page_directory(9)
• radeon_vm_update_ptes(9)
• radeon_vm_fence_pts(9)
• radeon_vm_bo_update(9)
• radeon_vm_clear_freed(9)
• radeon_vm_clear_invalids(9)
• radeon_vm_bo_rmv(9)
• radeon_vm_bo_invalidate(9)
• radeon_vm_init(9)
• radeon_vm_fini(9)

Source/version: ./drivers/gpu/drm/radeon · date: October 2026 · this page: radeon_vm_frag_ptes(9). Bye bestie, go lock those mutexes and slay 💖🦋✨