folio_add_anon_rmap_pmd(9)

📦 version 7.3.1, in nixpkgs unstable

💖 folio_add_anon_rmap_pmd 💖

okay bestie, so this is a page straight outta the Kernel API Manual and it's genuinely kinda iconic — it's about adding a PMD mapping to a page range of an anon folio. yes, that's a real sentence, and yes, we're gonna get through it together 🫶

✨ NAME ✨

folio_add_anon_rmap_pmd — add a PMD mapping to a page range of an anon folio 💅

🎀 SYNOPSIS 🎀

void folio_add_anon_rmap_pmd (struct folio *folio , struct page *page ,
       struct vm_area_struct *vma , unsigned long address , rmap_t flags );

like, look at her go. five arguments, zero notes 💀

🌸 ARGUMENTS 🌸

  • folio — the folio we're adding the mapping to, the main character ofc 👑
  • page — the first page to add. the opener, the headliner, page #1 ✨
  • vma — the vm area in which the mapping is added 🦋
  • address — the user virtual address of the first page to map 🎯
  • flags — the rmap flags. that's it, that's the whole description, ngl 🙈

🧚 DESCRIPTION 🧚

so the page range of folio is defined by [first_page, first_page + HPAGE_PMD_NR) — that bracket is closed on the left and open on the right, she's precise like that 💅

⚠️ real talk, bestie: the caller needs to hold the page table lock, and the page must be locked in the anon_vma case — that's to serialize mapping,index checking after setting. don't skip this, fr fr 😭

🌈 SEE ALSO 🌈

kernel file ./mm/rmap.c plus the whole friend group:

and that's the whole page, bestie, no cap 🍓 this lil gem lives over in ./mm and it's dated October 2026, filed under the Kernel API Manual — go off, folio_add_anon_rmap_pmd(9), you ate 💖✨

📦 where this page comes from