xe_svm_rang...tes_in_range(9)

okay so bestie, welcome to xe_svm_rang...tes_in_range(9) — yup, that's the page title — straight out of the Kernel API Manual ✨ This one is giving “page-table housekeeping but make it sparkle” 💅

🎀 NAME 🎀

xe_svm_ranges_zap_ptes_in_range — clears ptes of svm ranges in the input range. No cap, that's the whole name-and-purpose moment 🫶

🌸 SYNOPSIS 🌸

u8 xe_svm_ranges_zap_ptes_in_range (struct xe_vm *vm , u64 start , u64
       end );

🦋 ARGUMENTS 🦋

• vm — Pointer to the xe_vm structure. That's the VM bestie 💜
• start — Start of the input range. The beginning of the little range window ✨
• end — End of the input range. The finish line 🎀

💅 DESCRIPTION 💅

This function removes the page table entries (PTEs) associated with the svm ranges within the given input start and end. So like, it's doing PTE cleanup for svm ranges inside that start and end zone. Iconic, honestly 🔥

👑 RETURN 👑

Returns the tile_mask for which gt's need to be tlb invalidated. That's the return value, bestie — a tile_mask telling you which gt's need that tlb invalidation ☁️

🌈 SEE ALSO 🌈

Go touch grass in these related pages, iykyk:

• Kernel file ./drivers/gpu/drm/xe/xe_svm.c
• drm_pagemap reference-counting in xe:(9)
• 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_range_needs_migrate_to_vram(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_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)

signing off from source/version ./drivers/gpu/drm/xe — dated October 2026, page xe_svm_rang...tes_in_range(9) 💖✨