eeh_pe_get(9)

💖 NAME 💖

eeh_pe_get — search for a PE based on the given address, bestie ✨

So like, eeh_pe_get(9) is from the Kernel API Manual and it's literally the function you call when you need to go find a PE. Obsessed.

---

🌸 SYNOPSIS 🌸

struct eeh_pe * eeh_pe_get (struct pci_controller *phb , int pe_no );

---

🎀 ARGUMENTS 🎀

• phb — the PCI controller. That's your girl. The whole controller vibe.
• pe_no — the PE number. The number. The identifier. You need it, you got it.

---

🦋 DESCRIPTION 🦋

Okay so here's the tea ☕ — this function searches for the corresponding PE based on the specified address, and that address is included in the eeh device. The way it works is it's used to check if the associated PE has actually been created against the PE address. Vibe check on your PE, basically 💅

Now, it's notable — and I mean highkey notable, don't skip this — that the PE address has 2 formats:

1. the traditional PE address, which is composed of PCI bus/device/function number
2. the unified PE address

Two formats. No cap. Both real. 🫶

---

🔥 SEE ALSO 🔥

Kernel file ./arch/powerpc/kernel/eeh_pe.c — plus the whole friend group, fr fr:

• eeh_set_pe_aux_size(9)
• eeh_pe_alloc(9)
• eeh_phb_pe_create(9)
• eeh_wait_state(9)
• eeh_phb_pe_get(9)
• eeh_pe_next(9)
• eeh_pe_traverse(9)
• eeh_pe_dev_traverse(9)
• __eeh_pe_get(9)
• eeh_pe_tree_insert(9)
• eeh_pe_tree_remove(9)
• eeh_pe_update_time_stamp(9)
• eeh_pe_state_mark(9)
• eeh_pe_mark_isolated(9)
• eeh_pe_state_clear(9)
• eeh_restore_one_device_bars(9)
• eeh_pe_restore_bars(9)
• eeh_pe_loc_get(9)
• eeh_pe_loc_get_bus(9)
• _eeh_pe_bus_get(9)
• eeh_pe_bus_get(9)
• eeh_pe_bus_get_nolock(9)

---

Okay bye bestie, go read the source at ./arch/powerpc/kernel — this page was dated October 2026, and no I will not be elaborating further, mwah 💜✨🎀