xe_svm_range...rate_to_vram(9)
π 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β thevmathat has the rangedpagemapβ the preferredstruct drm_pagemapto 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:
xe_svm_init(9)xe_svm_close(9)xe_svm_fini(9)xe_svm_range_validate(9)xe_svm_find_vma_start(9)xe_svm_handle_pagefault(9)xe_svm_has_mapping(9)xe_svm_unmap_address_range(9)xe_svm_bo_evict(9)xe_svm_range_find_or_insert(9)xe_svm_range_get_pages(9)xe_svm_ranges_zap_ptes_in_range(9)xe_vma_resolve_pagemap(9)xe_svm_alloc_vram(9)xe_pagemap_create(9)xe_pagemap_find_or_create(9)xe_pagemap_shrinker_create(9)xe_pagemap_cache_create(9)xe_drm_pagemap_from_fd(9)xe_svm_flush(9)
xoxo, this cutie came from the ./drivers/gpu/drm/xe tree β October 2026 πβ¨ no cap, periodt.
π¦ 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