xe_sriov_vf_ccs_attach_bo(9)

✨ xe_sriov_vf_ccs_attach_bo ✨

okay bestie, welcome to the Kernel API Manual 💖 this is the page for xe_sriov_vf_ccs_attach_bo and honestly it's giving "small function, big job" energy. let's get into it 🎀

---

🌸 NAME 🌸

xe_sriov_vf_ccs_attach_bo — puts the CCS read/write commands into the BO. that's the whole vibe 🫶

---

✨ SYNOPSIS ✨

int xe_sriov_vf_ccs_attach_bo (struct xe_bo *bo , struct ttm_resource
       *new_mem );

like, two args, one int return, no cap 💅

---

🦋 ARGUMENTS 🦋

• bo — the buffer object that's gonna get the batch buffer commands added to it. that's the main character here 👑
• new_mem — the destination resource that bo is currently being moved into — and bestie, important detail: it is not yet committed at this point 😭 bo->ttm.resource is still pointing at the old resource while this is happening, so don't get it twisted 🙈

---

💜 DESCRIPTION 💜

so here's the tea ⭐ this function shall be called only by VF — like, that's a hard requirement, not a suggestion, periodt 🔥

what it actually does: it inserts the PTEs and the copy command instructions into the BO, and it does that by calling the xe_migrate_ccs_rw_copy function. that's it, that's the move 💫

fr fr, VF only. don't be out here calling it from anywhere else 🙅‍♀️

---

🌈 RETURN 🌈

• 0 if it worked — slay ✅
• a negative error code on failure — not slay, but at least it tells you 😭

---

🍓 SEE ALSO 🍓

• the kernel file ./drivers/gpu/drm/xe/xe_sriov_vf_ccs.c 📁
• VF save/restore of compression Meta Data(9)
• xe_sriov_vf_ccs_rebase(9)
• xe_sriov_vf_ccs_register_context(9)
• xe_sriov_vf_ccs_init(9)
• xe_sriov_vf_ccs_detach_bo(9) — the other half of this whole situation 👀
• xe_sriov_vf_ccs_print(9)

---

aaaand that's the page, bestie 🧚💖 this whole thing lives over in ./drivers/gpu/drm/xe, it's dated October 2026, and the page itself is xe_sriov_vf_ccs_attach_bo(9). go forth and attach those BOs responsibly 💅✨