i915_gem_ob...o_cpu_domain(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i915_gem_object_set_to_cpu_domain(9) πŸ’…

okay bestie, welcome to the Kernel API Manual, grab a strawberry πŸ“ and let me tell you about this little function. it lives in the i915 graphics corner of the kernel and it's genuinely iconic.


✨ NAME ✨

i915_gem_object_set_to_cpu_domain β€” Moves a single object to the CPU read, and possibly write domain.

like, one (1) object. not a group. not a bundle. a single one. main character energy only πŸ’…


🌸 SYNOPSIS 🌸

int i915_gem_object_set_to_cpu_domain (struct drm_i915_gem_object *obj ,
bool write );

it returns an int, takes a struct drm_i915_gem_object *obj, and a bool write. that's the whole vibe check.


πŸŽ€ ARGUMENTS πŸŽ€

  • obj β€” object to act on. yes queen, this is the thing you're moving 🫢
  • write β€” requesting write or read-only access. so like, are we just reading or are we also writing? you tell it.

πŸ¦‹ DESCRIPTION πŸ¦‹

This function returns when the move is complete, including waiting on flushes to occur.

read that again, bestie. it returns when the move is complete. it's not a "fire and forget" situation, it's a "we are doing this and you WILL wait" situation. and the waiting includes waiting on flushes to occur 😭 so if you were hoping to slide out early, no. not today. the flushes are happening and you're gonna sit there and watch, periodt.


πŸ’œ SEE ALSO πŸ’œ

the squad. the friend group. go read them too, iykyk ⭐


okay that's the page!! no cap, that's everything πŸ’– and now the cute little sign-off β€” this one comes from ./drivers/gpu/drm/i915/gem, dated October 2026, and it's filed under i915_gem_ob...o_cpu_domain(9). slay, bye πŸ§šβ€β™€οΈπŸŒˆ

πŸ“¦ where this page comes from