xe_bo_move_notify(9)

💅 xe_bo_move_notify(9) — Kernel API Manual, bestie edition

Okay so real quick, this page lives in the Kernel API Manual and it's literally all about telling everybody "hey, this buffer's about to move" before it actually does. Let's get into it 🫶

---

✨ NAME ✨

xe_bo_move_notify — notify subsystems of a pending move

Like, a heads-up text in the group chat before you start moving furniture, y'know?

---

🦋 SYNOPSIS 🦋

int xe_bo_move_notify (struct xe_bo *bo , const struct ttm_operation_ctx
*ctx );

---

🌸 ARGUMENTS 🌸

• bo — the buffer object in question, the main character of this whole operation 💖
• ctx — the struct ttm_operation_ctx that's controlling locking and waits. It's giving "adult supervision" energy ngl.

---

👑 DESCRIPTION 👑

So this function notifies subsystems that a buffer move is coming up. Like, upcoming, not happening right now. Rude to not warn a girl first, honestly.

When a subsystem gets this notification, it should schedule halting access to the underlying pages — and it optionally can add a fence to the buffer object's dma_resv object, which signals when access is stopped. Slay, that's how you communicate boundaries ✨

The caller will wait on all dma_resv fences before starting the move. No cutting the line, no skipping the wait, no cap.

A subsystem may commence access to the object after obtaining bindings to the new backing memory under the object lock. So like, you get the keys to the new place first, then you can start moving your stuff in. Periodt. 🔑

---

🔥 RETURN 🔥

• 0 on success — ate, no notes 💅
• -EINTR or -ERESTARTSYS if interrupted in fault mode — like getting a call mid-nap 😭
• a negative error code on error — yeah, that's the "it's giving problems" case 💀

---

💜 SEE ALSO 💜

Kernel file ./drivers/gpu/drm/xe/xe_bo.c and, honestly, 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_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_validate(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)

---

okay that's the whole page, you're officially smarter than you were three minutes ago, i'm so proud of you bestie 🧚💖

Oh and for the record — this one's from ./drivers/gpu/drm/xe, dated October 2026, and yes the date is in the future, don't ask, we don't question the timeline here ⭐