eeh_pe_bus_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… eeh_pe_bus_get(9) πŸ’…

okay so this is a page from the Kernel API Manual β€” yes, the Kernel API Manual, like, the real one β€” and it's all about eeh_pe_bus_get. bestie, grab a snack, this one's short and sweet πŸ“


✨ NAME ✨

eeh_pe_bus_get β€” retrieve the PCI bus associated with the given EEH PE, and it locks if needed πŸ”’


πŸŽ€ SYNOPSIS πŸŽ€

struct pci_bus * eeh_pe_bus_get (struct eeh_pe *pe );

🌸 ARGUMENTS 🌸

  • pe β€” pointer to the EEH PE. that's it, that's the whole argument list, she's low-maintenance πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

ok so picture this: this function is basically a wrapper around _eeh_pe_bus_get, which is the one doing the actual retrieving of the PCI bus tied to the EEH PE structure you handed over. main character energy, but with backup πŸ’–

the way that it works: it acquires the PCI rescans lock so that access to shared data stays safe the whole time it's doing the retrieval. no cap, that lock matters.

so when should you use this one? when you're the caller who needs the PCI bus while already holding the rescan/remove lock β€” typically during operations that modify or inspect PCIe device state in a safe manner. iykyk 🧚

πŸ‘‘ RETURN πŸ‘‘

a pointer to the PCI bus associated with the EEH PE β€” or NULL if none found. that's the whole vibe check πŸ™ˆ


⭐ SEE ALSO ⭐

kernel file ./arch/powerpc/kernel/eeh_pe.c, plus a whole friend group of functions:


and that's the whole page, bestie!! it came from ./arch/powerpc/kernel, dated October 2026, and it's literally called eeh_pe_bus_get(9) β€” go forth and lock responsibly πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from