STRUCT DRM_IVPU_BO_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct drm_ivpu_bo_info(9) β€” like, the Kernel API Manual page, bestie πŸŽ€

okay so first things first: this is a page straight outta the Kernel API Manual, and it's all about struct drm_ivpu_bo_info β€” yes, that's the whole vibe. It's the "Query buffer object info" struct, and honestly? She's giving lookup-table energy and I'm obsessed. ✨


🌸 NAME 🌸

struct drm_ivpu_bo_info β€” Query buffer object info 🫢

Like, you hand it a BO and it tells you stuff about it. That's the whole job. Iconic, honestly, no notes.


✨ SYNOPSIS ✨

struct drm_ivpu_bo_info {
    __u32 handle;
    __u32 flags;
    __u64 vpu_addr;
    __u64 mmap_offset;
    __u64 size;
 };

look at her. five fields. perfectly balanced. the way that __u32 and __u64 just coexist... πŸ’…


πŸ¦‹ Members πŸ¦‹

okay so let's go through the whole cast, one by one, main character by main character:

  • handle β€” Handle of the queried BO πŸ‘‘ β€” literally the ID of the buffer object you're asking about, iykyk.
  • flags β€” Returned flags used to create the BO πŸŽ€ β€” they come back to you from creation time, like a little receipt.
  • vpu_addr β€” Returned VPU virtual address ⭐ β€” the VPU's virtual address, returned to you, no cap.
  • mmap_offset β€” Returned offset to be used in mmap. 0 in case the BO is not mappable. 🌈 β€” yes bestie, that 0 means not mappable, don't come for me, that's just what it says.
  • size β€” Returned GEM object size, aligned to PAGE_SIZE πŸ’– β€” and it's aligned to PAGE_SIZE, so it's tidy. slay.
fr fr, mmap_offset being 0 is the "not mappable" signal β€” so if you see a 0 there, that's your answer, don't @ me. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

the whole group chat showed up for this one, and we're listing everyone, periodt:


πŸ’œ and that's the page!! sourced from ./include/uapi/drm, dated October 2026, and filed under struct drm_ivpu_bo_info(9) β€” mwah, go read the neighbors, ily, bye bestie πŸ§šπŸ’–

πŸ“¦ where this page comes from