pci_epc_mem_unmap(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pci_epc_mem_unmap(9) 💅

okay bestie, welcome to the Kernel API Manual, and today's main character is pci_epc_mem_unmap — the cleanup queen. She unmaps AND frees a CPU address region. That's it. That's her whole vibe. ✨

✨ SYNOPSIS ✨

void pci_epc_mem_unmap (struct pci_epc *epc , u8 func_no , u8 vfunc_no ,
       struct pci_epc_map *map );

returns nothing, void, because she's done after this, no notes 🎀

🌸 ARGUMENTS 🌸

  • epc — the EPC device on which the CPU address is allocated and mapped. like, the whole venue for this operation 🫶
  • func_no — the physical endpoint function number in the EPC device. lowkey important, this is the real one 💅
  • vfunc_no — the virtual endpoint function number in the physical function. the virtual lil sibling of func_no 🦋
  • map — the mapping information. she's literally carrying all the receipts of what got mapped 😭

💖 DESCRIPTION 💖

Here's the tea, bestie: this function unmaps and frees a CPU address region that was allocated and mapped with pci_epc_mem_map. it's giving cleanup era. you map it, you unmap it, balance is restored to the universe 🌈

no cap, she only takes care of stuff that pci_epc_mem_map set up — she's not out here cleaning up random addresses, so know your source 👑

🦋 SEE ALSO 🦋

Kernel file ./drivers/pci/endpoint/pci-epc-core.c — and honestly the whole friend group:

and that's the whole page, bestie!! 💜 this one lives in ./drivers/pci/endpoint and the version/date stamp on it is October 2026 — iconic, timeless, obsessed. go forth and unmap responsibly ✨🎀🦋

📦 where this page comes from