ttm_bo_pipeline_gutting(9)

ttm_bo_pipeline_gutting(9) 💖

okay bestie, this is the Kernel API Manual page for ttm_bo_pipeline_gutting(9) — yes, the title and the manual name are both right here, folded in like a cute little header moment. ✨ No cap, we’re about to get into it.

---

🌸 NAME 🌸

ttm_bo_pipeline_gutting — purge the contents of a bo.

---

✨ SYNOPSIS ✨

the signature is literally:

int ttm_bo_pipeline_gutting (struct ttm_buffer_object *bo );

---

🎀 ARGUMENTS 🎀

• bo — the buffer object. That’s the argument, bestie; it’s the buffer object and it’s the main character of this call. 💅

---

🦋 DESCRIPTION 🦋

okay so this function purges the contents of a bo — like, it clears the whole thing out. It does this async if the bo is not idle, so if the bo is already chilling/idle, that async vibe is not the move.

After a successful call, the bo is left unpopulated in system placement. That’s the after-state, periodt.

heads up, bestie: the function may wait uninterruptible for idle on OOM. So on OOM it can sit there waiting for idle and you can’t interrupt that wait — not me pretending that’s casual, because it’s literally in the docs. 😭

---

🌈 RETURN 🌈

Returns 0 if successful, and a negative error code on failure. fr fr, that’s the whole return contract.

---

👀 SEE ALSO 👀

Kernel file ./drivers/gpu/drm/ttm/ttm_bo_util.c — plus the whole bestie squad of related functions:

• ttm_move_memcpy(9)
• ttm_bo_move_memcpy(9)
• ttm_buffer_object_transfer(9)
• ttm_io_prot(9)
• ttm_bo_kmap_try_from_panic(9)
• ttm_bo_kmap(9)
• ttm_bo_kunmap(9)
• ttm_bo_vmap(9)
• ttm_bo_vunmap(9)
• ttm_bo_move_accel_cleanup(9)
• ttm_bo_move_sync_cleanup(9)
• ttm_lru_walk_for_evict(9)
• ttm_bo_lru_cursor_fini(9)
• ttm_bo_lru_cursor_init(9)
• ttm_bo_lru_cursor_next(9)
• ttm_bo_lru_cursor_first(9)
• ttm_bo_shrink(9)
• ttm_bo_shrink_suitable(9)
• ttm_bo_shrink_avoid_wait(9)

---

okay that’s the page, bestie! source/version: ./drivers/gpu/drm/ttm, dated October 2026 — and it’s the ttm_bo_pipeline_gutting(9) page. mwah 💋✨