xe_bo_validate(9)

💅 xe_bo_validate(9) — Kernel API Manual ✨

okay so bestie, welcome to the xe_bo_validate(9) page, straight out of the Kernel API Manual. this is the function that makes sure your buffer object is actually where it's supposed to be. no cap. let's get into it 🫶

---

🌸 NAME 🌸

xe_bo_validate — Make sure the bo is in an allowed placement 💖

like literally, that's the whole job. it checks the placement is legal and fixes it if not.

---

✨ SYNOPSIS ✨

int xe_bo_validate (struct xe_bo *bo , struct xe_vm *vm , bool
       allow_res_evict , struct drm_exec *exec );

it returns an int. that's gonna matter later, bestie. 👀

---

💅 ARGUMENTS 💅

• bo — The bo, ✨ (yes that's the entire description, she's brief, she's iconic, periodt).
• vm — Pointer to the vm the bo shares a locked dma_resv object with, or NULL. used together with allow_res_evict, so don't forget about her.
• allow_res_evict — Whether it's allowed to evict bos sharing the vm's reservation object. like, are we permitted to kick them out or not 🙈
• exec — The drm_exec transaction to use for exhaustive eviction. she's the paperwork for the whole eviction situation.

---

🔥 DESCRIPTION 🔥

So the vibe check here: xe_bo_validate makes sure the bo is in allowed placement, and it migrates it if necessary. migrating, moving, relocating — she does the work so you don't have to 💅

and if needed? other bos will be evicted. yes, evicted. it's giving real estate drama 😭.

here's the nuance though, and this part is important: if the bos selected for eviction share the vm's reservation object, they can be evicted iff allow_res_evict is set to true. otherwise they will be bypassed. so like, if that flag isn't set, those bos get skipped entirely — no eviction for them, no exceptions. iykyk 🎀

---

⭐ RETURN ⭐

• 0 on success 🎉 slay.
• a negative error code on failure, so watch out for that.
• it may return -EINTR or -ERESTARTSYS if internal waits are interrupted by a signal — so if a signal comes through mid-wait, that's what you get back, and it's not a bug, it's just how she works fr fr 💀

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/xe/xe_bo.c, plus the whole extended friend group:

• xe_bo_has_single_placement(9)
• xe_bo_is_stolen_devmem(9)
• xe_bo_is_vm_bound(9)
• xe_bo_pin_account(9)
• xe_bo_unpin_account(9)
• xe_bo_is_visible_vram(9)
• xe_bo_move_notify(9)
• xe_bo_set_purgeable_shrinker(9)
• xe_bo_set_purgeable_state(9)
• xe_ttm_bo_purge(9)
• xe_bo_shrink(9)
• xe_bo_notifier_prepare_pinned(9)
• xe_bo_notifier_unprepare_pinned(9)
• xe_bo_evict_pinned(9)
• xe_bo_restore_pinned(9)
• xe_bo_read(9)
• xe_bo_alloc(9)
• xe_bo_free(9)
• xe_bo_init_locked(9)
• xe_bo_create_locked(9)
• xe_bo_create_user(9)
• xe_bo_create_pin_range_novm(9)
• xe_bo_create_pin_map_at_novm(9)
• xe_bo_create_pin_map(9)
• xe_bo_create_pin_map_novm(9)
• xe_managed_bo_reinit_in_vram(9)
• xe_bo_pin_external(9)
• xe_bo_pin(9)
• xe_bo_unpin_external(9)
• xe_bo_decompress(9)
• xe_bo_lock(9)
• xe_bo_unlock(9)
• xe_bo_can_migrate(9)
• xe_bo_migrate(9)
• xe_bo_evict(9)
• xe_bo_needs_ccs_pages(9)
• __xe_bo_release_dummy(9)
• xe_bo_put_commit(9)
• xe_bo_dev_init(9)
• xe_bo_dev_fini(9)
• xe_bo_dumb_create(9)

---

ok that's the whole page bestie, you now know everything there is to know about validating a bo 🧚 go forth and place your buffer objects correctly. literally iconic of you. 💜

---

kisses, this one lives in ./drivers/gpu/drm/xe, dated October 2026, and that's the xe_bo_validate(9) sign-off 🍓💖