pvr_device_a...ze_are_valid(9)

💅 pvr_device_a...ze_are_valid(9) 💅

Okay so bestie, welcome to the Kernel API Manual — this one's about pvr_device_addr_and_size_are_valid, and like… the name literally spoils the whole plot but stay with me, it's actually a cute little corner-case baddie 🎀

---

✨ NAME ✨

pvr_device_addr_and_size_are_valid — it's the vibe-check function that tests whether a device-virtual address and its associated size are both valid. Two-for-one. A little duo. Periodt 💖

---

🦋 SYNOPSIS 🦋

bool pvr_device_addr_and_size_are_valid (struct pvr_vm_context *vm_ctx ,
u64 device_addr , u64 size );

---

🌸 ARGUMENTS 🌸

• vm_ctx — the target VM context. Like, the whole scene this function is operating in, y'know? 💜
• device_addr — the virtual device address you want to test, bestie.
• size — the size of the range based at device_addr that you're testing. It's giving "how much are we checking here" energy ✨

---

🧚 DESCRIPTION 🧚

So here's the tea ☕ — the obvious move is to call pvr_device_addr_is_valid twice: once on size, and again on device_addr + size. And honestly? It seems intuitive. Like, it lowkey looks correct. But it's NOT, because it produces a false-negative when the address range is right at the end of device-virtual address space 😭💀

This function catches that corner case — it's the main character that swoops in — and it also checks that size is non-zero. Two jobs. One icon 👑

---

🔥 RETURN 🔥

• true if device_addr is device page aligned; and size is device page aligned; and the range specified by device_addr and size is within the bounds of the device-virtual address space; and size is non-zero — like, all four, no skipping, okay? — or
• false otherwise 🫶

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/imagination/pvr_vm.c — and honestly the whole friend group:

• 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_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_find_heap_containing(9)
• pvr_vm_find_gem_object(9)
• pvr_vm_get_fw_mem_context(9)

---

Fr fr, that's the whole page. No cap. The address-range girly is valid or she isn't, and now you know exactly what "valid" means in this context 💅

---

And that's a wrap, bestie! 🎀 This gem came to you straight from ./drivers/gpu/drm/imagination and it's dated October 2026 — bookmark it, screenshot it, put it on your vision board 🌟 byeee 🦋💖