intel_context_is_pinned(9)
π intel_context_is_pinned (9) π
okay so welcome to the Kernel API Manual, bestie β this one's a tiny little function from the i915 world and honestly it's giving "small but crucial" β¨
πΈ NAME πΈ
intel_context_is_pinned β the one that reports the 'pinned' status π
π SYNOPSIS π
bool intel_context_is_pinned (struct intel_context *ce );
like, that's the whole vibe. one arg, one bool, no cap π
π¦ ARGUMENTS π¦
ceβ the context π«Ά that's it, that's the argument. it's thestruct intel_context *you're asking about.
β¨ DESCRIPTION β¨
okay so here's the tea π₯ β while the GPU is actually using a context, that context gets pinned into memory, and so do its ring and its page tables, and they all get pinned into the GTT too. so like, everything's locked down and staying put while it's in play. periodt π
this function is literally just the vibe check on that state π
π RETURN π
returns true if the context is currently pinned for use by the GPU β¨ (and, y'know, false if it's not β that's just how bool works, bestie π)
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/i915/gt/intel_context.hπ intel_context_lock_pinned(9)πintel_context_unlock_pinned(9)π
and that's the whole page, you ate that π β¨
cute lil sign-off time π β this one lives over in ./drivers/gpu/drm/i915/gt, dated October 2026, and it's intel_context_is_pinned(9) in case you need to cite it in the group chat. mwah, go forth and check your pinned status bestie π«Άπ
π¦ 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