i915_gem_ob..._struct_page(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

i915_gem_object_has_struct_page — bestie, this is the vibe check that tells you whether the object is page-backed ✨

So like, it's the Kernel API Manual entry (yes, that's the manual name, we're fancy here 🎀), and it's literally just asking one tiny question about a GEM object: does it have a struct page situation going on or not? Iconic, low-effort, high-value. 🦋

✨ SYNOPSIS ✨

bool i915_gem_object_has_struct_page (const struct drm_i915_gem_object
       *obj );

🫶 ARGUMENTS 🫶

  • obj — the object you're interrogating 👀. This is the const struct drm_i915_gem_object you want to query. That's it. That's the whole argument list. Slay.

🌸 DESCRIPTION 🌸

Okay so this is the important part, don't skip it 🙈 — this function should only be called while the object is locked or pinned. Like, only only. Because otherwise the page backing may change right out from under the caller mid-query, and that's giving chaos energy, not main character energy. 💀

Lock it or pin it first, bestie. No cap. The backing can literally shift under you if you don't. 😭

🔥 RETURN 🔥

  • Returns True if the object is page-backed 💖
  • Returns false otherwise 🫶

That's the whole answer. Binary. Clean. Periodt. 👑

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/i915/gem/i915_gem_object.c — go read it, iykyk 📖

And the whole friend group of related calls (we love a linked list of references, honestly obsessed):

and that's the whole page, bestie 🧚💜

Cute little sign-off so you know where this came from: it's from ./drivers/gpu/drm/i915/gem, dated October 2026, and it's the i915_gem_ob..._struct_page(9) page — yes the title is truncated in the middle like that, not me being dramatic, that's literally how it's printed 💅✨

📦 where this page comes from