xe_vma_need_vram_for_atomic(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ xe_vma_need_vram_for_atomic(9) ✨

okay so bestie, we're in the Kernel API Manual and this page is literally about xe_vma_need_vram_for_atomic(9) β€” the title is right there, we're being efficient πŸ’…

🌸 NAME 🌸

xe_vma_need_vram_for_atomic β€” check if VMA needs VRAM migration for atomic operations. That's the whole vibe check, no cap.

⭐ SYNOPSIS ⭐

int xe_vma_need_vram_for_atomic (struct xe_device *xe , struct xe_vma
       *vma , bool is_atomic );

πŸŽ€ ARGUMENTS πŸŽ€

Here's the cast, and yes they're all main characters:

  • xe β€” Pointer to the Xe device structure.
  • vma β€” Pointer to the virtual memory area (VMA) structure.
  • is_atomic β€” In pagefault path and atomic operation.

πŸ’– DESCRIPTION πŸ’–

This function determines whether the given VMA needs to be migrated to VRAM in order to do atomic GPU operation. So it's the "do we need to move this VMA to VRAM for this atomic GPU operation?" gatekeeper, and it hands you back a return value instead of just ✨vibes✨.

🌈 RETURN 🌈

  • 1 β€” Migration to VRAM is required.
  • 0 β€” Migration is not required.
  • -EACCES β€” Invalid access for atomic memory attr.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/gpu/drm/xe/xe_vm.c β€” and here's the whole friend group, zero skips:


xoxo, signing off from the source/version ./drivers/gpu/drm/xe, dated October 2026, on page xe_vma_need_vram_for_atomic(9) πŸ«ΆπŸ’…βœ¨

πŸ“¦ where this page comes from