pvr_find_heap_containing(9)

💖 pvr_find_heap_containing(9) 💖

okay so you're reading pvr_find_heap_containing(9) from the Kernel API Manual, bestie. It's the little function that goes “which heap contains this device-virtual address range?” and honestly? iconic. ✨

🌸 NAME 🌸

pvr_find_heap_containing — Find a heap which contains the specified device-virtual address range. That's the whole mission, no cap. 💅

🦋 SYNOPSIS 🦋

const struct drm_pvr_heap * pvr_find_heap_containing (struct pvr_device
       *pvr_dev , u64 start , u64 size );

🎀 ARGUMENTS 🎀

• pvr_dev — target PowerVR device. Like, the device you're checking against. 🫶
• start — start of the target range. The beginning, bestie. ⭐
• size — size of the target range. How much range we're talking about. 📏

🔥 RETURN 🔥

• A pointer to a constant instance of struct drm_pvr_heap representing the heap containing the entire range specified by start and size on success, or
• NULL if no such heap exists.

So yeah: you either get the heap pointer, or you get NULL and you deal with it. 😭

👀 SEE ALSO 👀

Go check out these little icons, iykyk:

• Kernel file ./drivers/gpu/drm/imagination/pvr_vm.c
• Memory context(9)
• struct pvr_vm_context(9)
• pvr_vm_get_page_table_root_addr(9)
• pvr_vm_get_dma_resv(9)
• Memory mappings(9)
• struct pvr_vm_gpuva(9)
• struct pvr_vm_bind_op(9)
• pvr_vm_bind_op_exec(9)
• pvr_vm_gpuva_map(9)
• pvr_vm_gpuva_unmap(9)
• pvr_vm_gpuva_remap(9)
• pvr_device_addr_is_valid(9)
• pvr_device_addr_and_size_are_valid(9)
• pvr_vm_create_context(9)
• pvr_vm_context_release(9)
• pvr_vm_context_lookup(9)
• pvr_vm_context_put(9)
• pvr_destroy_vm_contexts_for_file(9)
• pvr_vm_map(9)
• pvr_vm_unmap_obj_locked(9)
• pvr_vm_unmap_obj(9)
• pvr_vm_unmap(9)
• pvr_vm_unmap_all(9)
• pvr_heap_contains_range(9)
• pvr_vm_find_gem_object(9)
• pvr_vm_get_fw_mem_context(9)

Source/version vibe: ./drivers/gpu/drm/imagination · October 2026. That's the footer tea, bestie — bye! 🫶💖