__i915_gem_..._create_user(9)
π __i915_gem_..._create_user(9) β Kernel API Manual β¨
okay so bestie, welcome to the lil manpage for __i915_gem_..._create_user π this one lives in the Kernel API Manual and honestly it's giving "internal helper that knows what it's doing" energy π
πΈ NAME πΈ
__i915_gem_object_create_user β creates a new object using the same path as DRM_I915_GEM_CREATE_EXT π¦
β¨ SYNOPSIS β¨
struct drm_i915_gem_object * __i915_gem_object_create_user (struct
drm_i915_private *i915 , u64 size , struct intel_memory_region
**placements , unsigned int n_placements );
like literally that's the whole signature, no cap π«Ά
π ARGUMENTS π
i915β the i915 private struct, your main character π«Άsizeβ size of the buffer, in bytes πplacementsβ possible placement regions, in priority order β yes bestie, priority order, don't shuffle them πn_placementsβ number of possible placement regions π’
π DESCRIPTION π
so this function is exposed primarily for selftests π§ͺ like it's not out here doing the most for everyone, it's a selftest girlie. and it does very little error checking β not me showing up to the function with zero guardrails π
it is assumed that the set of placement regions has already been verified to be valid β so like, do that part yourself first, okay? it's not gonna double-check you. vibe check your placements before you call, fr fr π
π¦ SEE ALSO π¦
- Kernel file
./drivers/gpu/drm/i915/gem/i915_gem_create.cπ i915_gem_create_ioctl(9)i915_gem_create_ext_ioctl(9)
π‘ friendly reminder bestie: very little error checking means you are the error checking. slay responsibly π
that's the whole page!! source: ./drivers/gpu/drm/i915/gem, dated October 2026, and we're out π
β¨ bye bestie, go create some objects π
π¦ 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