ttm_tt_destroy(9)

💅 NAME 💅

ttm_tt_destroy — bestie, the description slot on this one is literally empty, no cap. The original page just goes ttm_tt_destroy - and then… nothing. Silence. Iconic of it, honestly. So here's what we've got: the name, the signature, and the tea in DESCRIPTION below. 🫶

(Also hi, this is the Kernel API Manual page for ttm_tt_destroy(9) — folding that in up top like a good little header, you're welcome ✨)

---

✨ SYNOPSIS ✨

void ttm_tt_destroy (struct ttm_device *bdev , struct ttm_tt *ttm );

That's it. That's the whole vibe. Two args, no return, void city. 🎀

---

🌸 ARGUMENTS 🌸

• bdev — the ttm_device this object belongs to. Like, whose house is this thing living in. 🏠
• ttm — the struct ttm_tt. Yes that's the entire description in the original and yes I'm keeping it because facts are facts. It's the struct ttm_tt, babe. 💅

---

🔥 DESCRIPTION 🔥

Okay so ttm_tt_destroy does the full goodbye tour, in order:

It unbinds, it unpopulates, and it destroys the common struct ttm_tt. Three stages. A whole farewell era. Not me getting emotional over a buffer object cleanup routine 😭

So like — think of it as the main character exit for a struct ttm_tt: it gets detached from where it was living, its memory situation gets cleared out, and then the thing itself gets yeeted into the void. Clean, complete, done. Periodt. 👑

---

🦋 SEE ALSO 🦋

Everything below is verbatim from the original, because I am not about to start beef with a cross-reference list. Iykyk. 💜

• Kernel file ./include/drm/ttm/ttm_tt.h
• struct ttm_tt(9)
• struct ttm_kmap_iter_tt(9)
• ttm_tt_is_swapped(9)
• ttm_tt_is_backed_up(9)
• ttm_tt_clear_backed_up(9)
• ttm_tt_create(9)
• ttm_tt_init(9)
• ttm_tt_fini(9)
• ttm_tt_swapin(9)
• ttm_tt_populate(9)
• ttm_tt_unpopulate(9)
• ttm_tt_mark_for_clear(9)
• struct ttm_backup_flags(9)
• ttm_agp_tt_create(9)

---

okay that's the whole page bestie, mwah 💖

Sign-off tea: this came out of the ./include/drm/ttm source, dated October 2026, and it's serving Kernel API Manual energy the whole way through. Go read the header file, it's giving lore. 🧚⭐