xe_svm_unmap_address_range(9)

🦋 xe_svm_unmap_address_range(9) 🦋

Okay so bestie, this is a page from the Kernel API Manual about xe_svm_unmap_address_range(9), and it's lowkey iconic in a tiny-kernel-function way. Let's unpack it together. 💖

✨ NAME ✨

xe_svm_unmap_address_range — UNMAP SVM mappings and ranges

🎀 SYNOPSIS 🎀

void xe_svm_unmap_address_range (struct xe_vm *vm , u64 start , u64 end
);

💅 ARGUMENTS 💅

• vm — The VM. That's the whole description, and honestly? Respect. 🫶
• start — start addr — the starting address, periodt.
• end — end addr — the ending address, no cap.

🌸 DESCRIPTION 🌸

This function UNMAPS svm ranges if start or end address are inside them. That's it — that's the assignment. If either address is inside an svm range, this function goes ahead and UNMAPS those svm ranges.

The condition is literally start or end being inside the ranges, bestie. No extra lore, no secret side quest. 💀

💖 SEE ALSO 💖

• 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_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)

Okay that's the whole page, bestie. Cute little footer sign-off: source/version ./drivers/gpu/drm/xe, dated October 2026, and yes the footer still reps xe_svm_unmap_address_range(9). Stay hydrated and may your address ranges never surprise you. 💜