ttm_pool_backup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, this page is ttm_pool_backup(9) from the Kernel API Manual, and it is literally about backing up or purging a struct ttm_tt πŸ’–.

  • ttm_pool_backup β€” back up or purge a struct ttm_tt.

✨ SYNOPSIS ✨

long ttm_pool_backup (struct ttm_pool *pool , struct ttm_tt *tt , const
struct ttm_backup_flags *flags );

🫢 ARGUMENTS 🫢

  • pool β€” the pool used when allocating the struct ttm_tt.
  • tt β€” the struct ttm_tt.
  • flags β€” flags to govern the backup behaviour.

πŸ’… DESCRIPTION πŸ’…

Back up or purge a struct ttm_tt. No cap, that’s the whole vibe.

If purge is true, then all pages will be freed directly to the system rather than to the pool they were allocated from, making the function behave similarly to ttm_pool_free. If purge is false, the pages will be backed up instead, exchanged for handles ✨. A subsequent call to ttm_pool_restore_and_alloc will then read back the content, and a subsequent call to ttm_pool_drop_backed_up will drop it.

If backup of a page fails for whatever reason, ttm will still be partially backed up, retaining those pages for which backup fails. In that case, this function can be retried, possibly after freeing up memory resources. That part is important, bestie 🫢.


🌈 RETURN 🌈

Returns the number of pages actually backed up or freed, or a negative error code on error.


πŸ‘‘ SEE ALSO πŸ‘‘


mwah πŸ’‹ this lil page came from source/version ./drivers/gpu/drm/ttm, dated October 2026, and it’s ttm_pool_backup(9) β€” bye bestie! 🫢✨

πŸ“¦ where this page comes from