pci_epc_unmap_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pci_epc_unmap_addr(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so real talk, this is a page from the Kernel API Manual, and the star of the show is pci_epc_unmap_addr πŸ’–


✨ NAME ✨

pci_epc_unmap_addr β€” unmap CPU address from PCI address πŸ¦‹

Literally what it says on the tin: it unhooks a CPU address from a PCI address. The un-map. The breakup arc. πŸ’”


🌸 SYNOPSIS 🌸

void pci_epc_unmap_addr (struct pci_epc *epc , u8 func_no , u8 vfunc_no
, phys_addr_t phys_addr );

notice how it returns void? yeah, it's not giving you anything back, it's giving you closure and that's it πŸ’€


🫢 ARGUMENTS 🫢

  • epc β€” the EPC device on which address is allocated. like, the actual device this whole thing lives on, okay? 🏠
  • func_no β€” the physical endpoint function number in the EPC device. the physical one, keep that straight ✨
  • vfunc_no β€” the virtual endpoint function number in the physical function. yes there's a virtual one too, it's giving layers πŸ‘‘
  • phys_addr β€” physical address of the local system. the local one, bestie, don't get it twisted 🌈

🧚 DESCRIPTION 🧚

Invoke this when you need to unmap the CPU address from the PCI address. that's the whole vibe. it's the undo button, the "jk", the never mind πŸ’…βœ¨

ngl this is the counterpart operation β€” you mapped it, now you're un-mapping it. no cap, that's the entire description in the source, so I'm not gonna manifest extra lore that isn't there πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

that's a whole friend group fr fr, they all ate πŸ’–


and that's the page, bestie! cute lil sign-off: this one's filed under ./drivers/pci/endpoint and dated October 2026, so mark your calendar πŸŽ€βœ¨πŸ¦‹ slay, you now understand pci_epc_unmap_addr(9), periodt πŸ’œ

πŸ“¦ where this page comes from