pci_epc_mem_alloc_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ 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 its size_t glory ✨

πŸ’œ 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 πŸ’€


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