drm_pagemap_evict_to_ram(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_pagemap_evict_to_ram(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual page for drm_pagemap_evict_to_ram β€” it's giving β€œevict this GPU SVM range to RAM” and honestly? iconic. πŸ’…


🌸 NAME 🌸

drm_pagemap_evict_to_ram β€” Evict GPU SVM range to RAM

✨ SYNOPSIS ✨

int drm_pagemap_evict_to_ram (struct drm_pagemap_devmem
*devmem_allocation );

πŸŽ€ ARGUMENTS πŸŽ€

  • devmem_allocation β€” pointer to the device memory allocation. that's the pointer you're handing over, bestie 🫢

πŸ’… DESCRIPTION πŸ’…

So this one is similar to __drm_pagemap_migrate_to_ram, but it uses the migrate_device_* helpers and does not require the mmap lock. no cap, that lock is not invited to this party πŸ™ˆ

Also: device-private PFNs already migrated to RAM by either path are skipped. like, β€œbeen there, done that, not doing it again” energy. skipped. periodt. ✨

πŸ¦‹ RETURN πŸ¦‹

0 on success, negative error code on failure. that's the whole vibe check: 0 means slay, negative means something went wrong and you get an error code 😭

πŸ‘‘ SEE ALSO πŸ‘‘


that's the page, bestie 🫢 source/version vibes from ./drivers/gpu/drm, dated October 2026. mwah πŸ’‹πŸŒˆ

πŸ“¦ where this page comes from