i915_gem_object_is_lmem(9)
β¨ 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 π₯
- Kernel file
./drivers/gpu/drm/i915/gem/i915_gem_lmem.c __i915_gem_object_create_lmem_with_ps(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms