vmw_bo_sg_table(9)

💖 NAME 💖

Okay bestie, welcome to the Kernel API Manual page for vmw_bo_sg_table(9) — manual name folded in right here, cute and all. ✨

• vmw_bo_sg_table — return a struct vmw_sg_table object for a TTM buffer object. That's the whole assignment, no cap. 💅

---

✨ SYNOPSIS ✨

Here's the exact signature — do not freestyle it, bestie:

const struct vmw_sg_table * vmw_bo_sg_table (struct ttm_buffer_object
*bo );

---

🎀 ARGUMENTS 🎀

• bo — pointer to a struct ttm_buffer_object. That's the only argument, and yes, it's giving very important pointer energy. 🫶

---

🦋 DESCRIPTION 🦋

This function returns a pointer to a struct vmw_sg_table object. The object should not be freed after use — like, do not go freeing it, okay? 🚫💀

That's literally the returned object's whole boundary situation. Respect it.

⚠️ Validity check: for the device addresses to be valid, the buffer object must either be reserved or pinned. That's the vibe check for whether those addresses are actually valid. 💅✨

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c — that's the path, iykyk. 🧚

• __vmw_piter_non_sg_next(9)
• vmw_piter_start(9)
• vmw_ttm_unmap_from_dma(9)
• vmw_ttm_map_for_dma(9)
• vmw_ttm_map_dma(9)
• vmw_ttm_unmap_dma(9)
• vmw_move_notify(9)
• vmw_swap_notify(9)

---

That's the whole page, bestie. Stay iconic, keep your buffer-object validity situation in check, and remember: no freeing the returned object after use. 💜 This one lives under ./drivers/gpu/drm/vmwgfx, is dated October 2026, and is proudly the vmw_bo_sg_table(9) page from the Kernel API Manual. periodt. ✨👑