drm_pagemap_populate_mm(9)

📦 version 7.3.1, in nixpkgs unstable

💖 drm_pagemap_populate_mm(9) — Kernel API Manual 💖

okay so bestie, we're looking at drm_pagemap_populate_mm(9) from the Kernel API Manual, and it's lowkey a whole moment. 🫶 Let's get into it.

✨ NAME ✨

drm_pagemap_populate_mm — Populate a virtual range with device memory pages ✨

🌸 SYNOPSIS 🌸

int drm_pagemap_populate_mm (struct drm_pagemap *dpagemap , unsigned
       long start , unsigned long end , struct mm_struct *mm , unsigned long
       timeslice_ms );

🎀 ARGUMENTS 🎀

  • dpagemap — Pointer to the drm_pagemap managing the device memory. That's the main character doing the managing. 👑
  • start — Start of the virtual range to populate.
  • end — End of the virtual range to populate.
  • mm — Pointer to the virtual address space.
  • timeslice_ms — The time requested for the migrated pagemap pages to be present in mm before being allowed to be migrated back. Basically the "stay here for this long" timer, fr fr. ⏳

🦋 DESCRIPTION 🦋

Attempt to populate a virtual range with device memory pages, clearing them or migrating data from the existing pages if necessary. The function is best effort only, and implementations may vary in how hard they try to satisfy the request. So like, no cap: it's gonna try, but the effort level can vary depending on the implementation. 💅

🔥 RETURN 🔥

0 on success, negative error code on error.

If the hardware device was removed / unbound the function will return -ENODEV. Bestie, that's the "device said bye" era. 💀

🌈 SEE ALSO 🌈

xoxo, your kernel bestie 💅 — this iconic little page is brought to you by source/version ./drivers/gpu/drm, dated October 2026, for drm_pagemap_populate_mm(9) 🎀

📦 where this page comes from