xe_svm_range_validate(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 xe_svm_range_validate(9) 🦋 — welcome to the Kernel API Manual, bestie!

okay so you clicked into the Kernel API Manual page for xe_svm_range_validate(9), and honestly? iconic choice. let's get into it 💅

💖 NAME 💖

xe_svm_range_validate — check if the SVM range is valid. that's the vibe check, fr fr 🫶

✨ SYNOPSIS ✨

the signature, untouched and looking gorgeous:

bool xe_svm_range_validate (struct xe_vm *vm , struct xe_svm_range
       *range , u8 tile_mask , const struct drm_pagemap *dpagemap );

🎀 ARGUMENTS 🎀

bestie, here's the whole cast — every single one matters:

  • vm — an xe_vm pointer. yes, literally that.
  • range — pointer to the SVM range structure. main character energy, honestly.
  • tile_mask — mask representing the tiles to be checked. the way that this mask is masking 😭
  • dpagemap — if !NULL, the range is expected to be present in device memory identified by this parameter. no cap, that !NULL detail is important 💀

🌸 DESCRIPTION 🌸

the xe_svm_range_validate function checks if a range is valid and located in the desired memory region.

that's it. that's the whole function. it's not here to start drama, it's just doing its little validity check and memory-region vibe check. periodt ✨

🔥 RETURN 🔥

  • true if the range is valid
  • false otherwise

literally binary. she ate and left no crumbs 🍓

💜 SEE ALSO 💜

okay so the lore is deep, and every one of these is right there — don't skip them:

source/version: ./drivers/gpu/drm/xe · date: October 2026 · stay slay, drink water, and validate your ranges 💖🦋

📦 where this page comes from