ttm_backup_copy_page(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 ttm_backup_copy_page(9) — the kernel API manual, bestie edition ✨

Okay so picture this: it's giving kernel API manual, it's in section 9, and it's literally about copying a page that you already backed up. The way that this function is just here to put your data back where it belongs 🫶. Buckle up, this one's short but she's important.

✨ NAME ✨

ttm_backup_copy_page — copy the contents of a previously backed up page 💅

🌸 SYNOPSIS 🌸

int ttm_backup_copy_page (struct file *backup , struct page *dst ,
pgoff_t handle , bool intr , gfp_t additional_gfp );

Like, that's the whole signature. Five args, one int back. Iconic.

🎀 ARGUMENTS 🎀

  • backup — the struct backup pointer that was used to back up the page. Your little backup handle bestie 🥰
  • dst — the struct page you're copying into. Destination era ✨
  • handle — the handle that got returned when the page was backed up. Gotta have the receipt, iykyk.
  • intr — try to perform the waits interruptible, or at least killable. Basically: do you want to be politely interruptible or nah 💀
  • additional_gfp — the GFP mask to add to the default GFP mask, if there is one. Extra mask energy 🧚

⭐ RETURN ⭐

  • 0 on success — slay, we ate 💖
  • Negative error code on failure — and notably -EINTR if intr was set to true and a signal is pending. Like, a signal showed up mid-wait and was like "girl, not right now" 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/ttm/ttm_backup.c, plus the whole backup friend group:

Heads up bestie: if you pass intr = true and there's a signal pending, don't be shocked when you get -EINTR back instead of a 0. That's her whole personality, no cap 💅

And that's the whole read, babe 🫶. This lil page lives in ./drivers/gpu/drm/ttm, dated October 2026, and it's from the Kernel API Manual — go forth and copy those pages with main character energy, periodt. 🦋✨🎀

📦 where this page comes from