pci_epc_mem_alloc_addr(9)
π pci_epc_mem_alloc_addr(9) π
okay so bestie, welcome to the Kernel API Manual π this one lives in section 9 and it's literally the glow-up your EPC address space has been waiting for. no cap.
β¨ NAME β¨
pci_epc_mem_alloc_addr β grab a memory address out of the EPC addr space, slay π
πΈ SYNOPSIS πΈ
void __iomem * pci_epc_mem_alloc_addr (struct pci_epc *epc , phys_addr_t
*phys_addr , size_t size );
π¦ ARGUMENTS π¦
epcβ the EPC device you're allocating memory on, like obviously, it's the main character here πphys_addrβ you drop the allocated physical address in here, she's an out-param and she's serving π«Άsizeβ how much address space you want, in all itssize_tglory β¨
π DESCRIPTION π
okay so the whole vibe: you invoke this when you need to allocate a memory address from the EPC address space. and like, why would you? the usual reason is to map the remote RC address into the local system β that's it, that's the tea π ngl it's pretty iconic.
π SEE ALSO π
Kernel file ./drivers/pci/endpoint/pci-epc-mem.c β go read her, she ate π
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_free_addr(9)
and that's the whole page, bestie π this one's from the kernel API manual, lives in ./drivers/pci/endpoint, dated October 2026 β no gatekeeping, go forth and allocate π§ββοΈβ¨ periodt.
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms