panthor_vm_get_bo_for_va(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– panthor_vm_get_bo_for_va(9) πŸ’–

okay so bestie, this is a page from the Kernel API Manual β€” welcome to the panthor zone πŸ¦‹


✨ NAME ✨

panthor_vm_get_bo_for_va β€” get the GEM object mapped at a virtual address πŸŽ€


🌸 SYNOPSIS 🌸

struct panthor_gem_object * panthor_vm_get_bo_for_va (struct panthor_vm
*vm , u64 va , u64 *bo_offset );

πŸ’… ARGUMENTS πŸ’…

  • vm β€” the VM we're looking into, like your search bar but for GPU memory 🫢
  • va β€” the virtual address to search for, the thing we're hunting down ✨
  • bo_offset β€” the offset of the GEM object mapped at this virtual address. Heads up: this is only valid on success, so don't go reading it if things went sideways 😭

πŸ”₯ DESCRIPTION πŸ”₯

The object returned by this function might no longer be mapped when the function returns. Yeah, I know. It's giving "here's your answer but also maybe not."

It's the caller's responsibility to make sure there's no concurrent map/unmap operations making the returned value invalid β€” or to make sure it doesn't matter if the object is no longer mapped. Either way, bestie, that's on you πŸ’€

no cap, this is a real caveat β€” the page literally says the mapping can vanish out from under you. Plan accordingly πŸ‘‘

⭐ RETURN ⭐

A valid pointer on success, an ERR_PTR otherwise. That's it, that's the vibe check βœ…


πŸ¦‹ SEE ALSO πŸ¦‹

First up, the source file to go look at: ./drivers/gpu/drm/panthor/panthor_mmu.c πŸ‘€

And a whole friend group of related structs and functions, all present and accounted for:


and that's the whole page, bestie πŸŽ€ this icon of a manpage lives under ./drivers/gpu/drm/panthor, dated October 2026 β€” slay, go read the rest of the panthor saga πŸ’œβœ¨

πŸ“¦ where this page comes from