xe_svm_range...rate_to_vram(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– xe_svm_range_needs_migrate_to_vram(9) πŸ’–

okay bestie, welcome to the Kernel API Manual ✨ this page is here to answer one very specific question: does this SVM range need to migrate to VRAM, or not? lowkey important, highkey iconic.


🌸 NAME 🌸

xe_svm_range_needs_migrate_to_vram β€” tells you whether an SVM range needs to migrate to VRAM or not. that's the whole vibe 🫢


✨ SYNOPSIS ✨

bool xe_svm_range_needs_migrate_to_vram (struct xe_svm_range *range ,
       struct xe_vma *vma , const struct drm_pagemap *dpagemap );

πŸŽ€ ARGUMENTS πŸŽ€

  • range β€” the SVM range where we're deciding if migration needs to happen πŸ‘€
  • vma β€” the vma that has the range
  • dpagemap β€” the preferred struct drm_pagemap to migrate to πŸ’…

πŸ’… RETURN πŸ’…

True for a range that needs migration and migration is supported β€” else false πŸ¦‹


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpu/drm/xe/xe_svm.c, plus drm_pagemap reference-counting in xe:(9), and all these iconic friends:


xoxo, this cutie came from the ./drivers/gpu/drm/xe tree β€” October 2026 πŸ’–βœ¨ no cap, periodt.

πŸ“¦ where this page comes from