devm_memremap_pages(9)

💅 NAME

devm_memremap_pages — bestie, this one remaps stuff and hooks you up with memmap backing for the given resource ✨

(also hi, welcome to the Kernel API Manual 🎀)

✨ SYNOPSIS ✨

void * devm_memremap_pages (struct device *dev , struct dev_pagemap *pgmap );

🫶 ARGUMENTS

• dev — the hosting device for res, no cap 🦋
• pgmap — a pointer to a struct dev_pagemap, that's literally the whole vibe

🔥 NOTES 🔥

Okay so there are like four things you absolutely have to know before you go in, and I'm gonna say them in order because that's just how I am 💅

1. Minimum effort is not it here, bestie — the caller has to initialize the range and type members of pgmap before passing it to this function. Like, before. Not later. 😭
2. The altmap field is optional, you may initialize it — but if you do, PGMAP_ALTMAP_VALID must be set in pgmap->flags. It's giving package deal. 🎀
3. The ref field is also optional, in which pgmap->ref must be devm_memremap_pages_release time, or if this routine fails. (that's exactly how the manual says it, I'm not editing the queen's words 👑)
4. range is expected to be a host memory range that could feasibly be treated as a "System RAM" range — i.e. not a device mmio range. But real talk: this is not enforced. So like… no one's gonna stop you, but also, choices. 💀

🌈 SEE ALSO

• Kernel file ./mm/memremap.c
• get_dev_pagemap(9)

okay that's the whole page, mwah 🫶 this little gem lives in ./mm, it's dated October 2026, and it's filed under devm_memremap_pages(9) in the Kernel API Manual — go forth and remap responsibly ✨💖