pci_epc_mem_free_addr(9)

💖 pci_epc_mem_free_addr — the kernel API glow-up 💖

Okay bestie, so this little function lives in the Kernel API Manual and honestly? It's giving "cleanup era." It's the responsible bestie who shows up after the party (aka pci_epc_mem_alloc_addr) to make sure everything gets tidied away properly. No leaks, no mess, periodt. 🎀

✨ SYNOPSIS ✨

void pci_epc_mem_free_addr (struct pci_epc *epc , phys_addr_t phys_addr
, void __iomem *virt_addr , size_t size );

🌸 ARGUMENTS 🌸

• epc — the EPC device that the memory was originally allocated on. Like, the actual host of the whole situation. 👑
• phys_addr — the physical address that got allocated. The real-world coordinates of your memory, iykyk. 🗺️
• virt_addr — the virtual address of the allocated memory space. Bestie's POV version of the same spot. 🦋
• size — the size of the allocated address space. Gotta know how much you're handing back, no cap. 📏

💅 DESCRIPTION 💅

So here's the tea: you invoke this when you wanna free the memory that was allocated using pci_epc_mem_alloc_addr. It's the undoing, the reverse uno card, the "okay we're done here" moment. Literally just call it and let it handle the rest. ✨

🔥 SEE ALSO 🔥

• Kernel file ./drivers/pci/endpoint/pci-epc-mem.c — the whole vibe lives here, highly recommend a read. 📖
• pci_epc_mem_get_order(9)
• pci_epc_multi_mem_init(9)
• pci_epc_mem_init(9)
• pci_epc_mem_exit(9)
• pci_epc_mem_alloc_addr(9) — the og allocator, this function's main character counterpart. 🫶

ngl, always pair this with pci_epc_mem_alloc_addr or you'll be leaking memory and that's not the aesthetic. 💀

And that's the whole page, bestie! Sourced from ./drivers/pci/endpoint, dated October 2026, and filed under the pci_epc_mem_free_addr(9) manual. Slay, go free that memory. 🌈💜