i915_gem_object_is_lmem(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ i915_gem_object_is_lmem(9) ✨

okay so bestie, buckle up β€” this is a kernel API manual page, aka the i915_gem_object_is_lmem page from the Kernel API Manual. yes it's a mouthful, no you cannot skip it πŸ’…


🌸 NAME 🌸

i915_gem_object_is_lmem β€” literally just answers the question: is this object resident in lmem? that's it, that's the whole vibe check πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

bool i915_gem_object_is_lmem (struct drm_i915_gem_object *obj );

it returns a bool. iconic. returns a yes-or-no, a slay-or-slayn't πŸ’–


🫢 ARGUMENTS 🫢

  • obj β€” the object you're checking. that's the one. the main character of this function call πŸ‘‘

🧚 DESCRIPTION 🧚

so here's the situation, ngl it's a little nuanced πŸ™ˆ

even if an object is allowed to migrate and change its memory region, this function still checks whether it will always be present in lmem when valid β€” or, if that's not the case, whether it's currently resident in lmem. two different questions, one function, we love a multitasker ✨

for migratable and evictable objects, that second check (the "currently resident" one) only makes sense when the object is locked πŸ”’ β€” like, do not even try it unlocked, that's not the move, that's not the era πŸ’€

🌈 RETURN 🌈

it returns whether the object is migratable but resident in lmem, or not migratable and will be present in lmem when valid. so basically: yes in one way, or yes in the other way. either way you're getting your answer, periodt 🫢


πŸ”₯ SEE ALSO πŸ”₯


and that's the page, bestie!! πŸŽ€βœ¨ this little gem lives in ./drivers/gpu/drm/i915/gem, it's dated October 2026, and it's part of the Kernel API Manual β€” go forth and check your lmem, ily, bye πŸ’œπŸ¦‹

πŸ“¦ where this page comes from